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've been experimenting with the builders, and I think we should build most of the files to the cache rather than to source. We have 10 builders now, and the number of generated files is overwhelming.
Do any builders other than req_builder and data_builder really need to be built to source?
The text was updated successfully, but these errors were encountered:
smkhalsa
changed the title
[gql_build] Built to cache
[gql_build] Build to cache
Jan 21, 2020
I'm not sure about the implications of building to cache. If you play around and see it works well for cli, web and flutter, I'm open to such change.
An alternative I had in mind was something similar to part builder, where there is a post-processor which bundles built files into a single file. I think it is useful to see the genarated code.
I do not know what works the best, but I can certainly agree that there are too many files being generated.
Another thing to keep in mind is that some of the builders should be useful on their own, like AST builder which can be used in both Artemis and graphql-flutter.
I've been experimenting with the builders, and I think we should build most of the files to the cache rather than to source. We have 10 builders now, and the number of generated files is overwhelming.
Do any builders other than
req_builder
anddata_builder
really need to be built to source?The text was updated successfully, but these errors were encountered: