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
Currently, when Sapling digests config.json, permissions.json, hooks.json, methods and routing, they're all tightly coupled with initialising them for use.
However, this makes it hard for the GUI to extract the digested configuration for display.
Extract these from the core methods into separate, independently importable and runnable methods.
The text was updated successfully, but these errors were encountered:
Unclear whether it would be cleaner to extract them as separate files that the core methods (and GUI) can import, or whether the core files should export the current default and a config digestion method from the same file.
Currently, when Sapling digests
config.json
,permissions.json
,hooks.json
, methods and routing, they're all tightly coupled with initialising them for use.However, this makes it hard for the GUI to extract the digested configuration for display.
Extract these from the core methods into separate, independently importable and runnable methods.
The text was updated successfully, but these errors were encountered: