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
Further progress on the #780 config testing is showing that a config root using ConfigPhase.BUILD_AND_RUN_TIME_FIXED does not see the build time values restored by the generated ConfigHelper class. I'm guessing that an ObjectSubstitution is not being generated, but need to look into this more.
The text was updated successfully, but these errors were encountered:
All that is being generated is the default initialization code. The ObjectSubstitution approach will not work as I'm looking at the code because the generated ObjectLoader takes precedence. The initialization code simply needs to be a serialization of the object. Is there a utility/code that writes out an object in gizmo or the codebase?
No, it's a bit more complex than that unfortunately. My current plan is to bake the build config in as a build-config.properties and load it in a separate pass during static init using the same loader code.
The ConfigDefinition class was designed to be a monolithic view of all config, but now it seems like it might be better to have some kind of better separation between build config, build config that's visible at run time, and run time config. This also ties into #860 and needing to load the run time config during the main method only, so I can support command line arguments which affect config processing.
Further progress on the #780 config testing is showing that a config root using ConfigPhase.BUILD_AND_RUN_TIME_FIXED does not see the build time values restored by the generated ConfigHelper class. I'm guessing that an ObjectSubstitution is not being generated, but need to look into this more.
The text was updated successfully, but these errors were encountered: