Separate subdirectory for result types #261
Closed
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.
Dear Maintainers,
I am excited to propose an enhancement to library, which I believe will improve its usability.
Issue Addressed:
Currently, the library's hundreds of modules, including client enums, inputs, fragments, and the client itself, are housed in a single package directory. More information is available in the issue.
Proposed Change:
To address this, I have implemented a feature that allows result types to be saved into a separate subdirectory. This feature is disabled by default and have no breaking changes for current users.
Implementation Details:
result_types_directory_name
, has been introduced. Users can specify the name of the subdirectory for result types using this parameter. If this parameter is omitted or left empty, the result types will be stored in the package root, maintaining the existing behavior.Thank you for your time and for considering this contribution to the project. If you have any suggestions or remarks about the code changes, please feel free to comment here, and I will do my best to find a better solution.
Best regards,
Alex