You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on creating a generator that collects all the necessary mocks to initialize a class. These mocks are generated using Sourcery, and it appears that the only way to include them in the source files is by appending extension to their filenames and using the extension in --force-parse argument.
However, for the past years, we've been generating mocks without needing to add any additional extensions like ".generated." to their filenames. This new requirement is causing some issues with our workflow.
Is there any workaround or configuration setting that would allow us to continue using these generated mocks without modifying their filenames to include specific extensions? Any guidance or suggestions would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Sourcery never scanned code that was generated by Sourcery, it's a chicken and egg situation and could cause very weird and inconsistent behaviour, that's why we added --force-parse, if someone really needs 2 pass then they can use it, but not in regular execution flow
I'm working on creating a generator that collects all the necessary mocks to initialize a class. These mocks are generated using Sourcery, and it appears that the only way to include them in the source files is by appending extension to their filenames and using the extension in --force-parse argument.
However, for the past years, we've been generating mocks without needing to add any additional extensions like ".generated." to their filenames. This new requirement is causing some issues with our workflow.
Is there any workaround or configuration setting that would allow us to continue using these generated mocks without modifying their filenames to include specific extensions? Any guidance or suggestions would be greatly appreciated.
The text was updated successfully, but these errors were encountered: