Open devmil opened 3 days ago
please, please, do like json_serializable and other packaged builders, and split reflectable into 2 different packages, 1 for the builder and another for the annotation, so we don't need to introduce a lot of unneeded dependencies beyond the dev dependencies declaration!
Makes sense. I'll take a look.
We currently face an issue where a library we use, uses reflectable and therefore transitively introduces the Builder bundled with reflectable. We have a highly dynamic and huge package landscape and a couple of them use other Builders to generate code. The reflectable Builder is now causing issues (out of memory) and all those packages need to disable the reflector Builder in their build.yaml to continue working.
I think it would be better to have the Builder separated so that it can be used as a dev dependency not leaking it to all consumers.