feat: add option to customize API client constructor name #320
+4,367
−4,908
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR introduces the ability to customize the export name of the API client constructor in the Handlebars (.hbs) template. Previously, the constructor function was exported with a fixed name, limiting flexibility in different use cases. Now, the export name is dynamically assigned based on options.apiClientConstructorName, with a default fallback (createApiClient), maintaining the original fixed name when no custom name is provided when no custom name is provided.
Motivation:
This change allows developers to specify a custom name for the API client constructor, improving integration flexibility.