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
When working with Neos I often struggle to find out, which configuration of my nodetypes or fusion prototypes are actually loaded at runtime. At runtime neos collects all the files and "constructs" the effective nodetype configuration by plugging together the yaml or fusion, overriding keys depending on package loading order and so on.
It is hard to keep track, what is actually happening.
I'm dreaming of a feature that shows me the effective configuration when hovering over a nodetype or fusion prototype.
As there is a backend view for all of this (which is far away for me while I'm developing from IntelliJ) I assume that this could be generated by periodically running the flow binary via the plugin or something (e.g. when triggering a save)?
Would even be cooler to add something like git blame to that view that shows where a certain key's value comes from (which file or package), to track down problems when overriding keys in fusion or nodetype definitions.
The text was updated successfully, but these errors were encountered:
When working with Neos I often struggle to find out, which configuration of my nodetypes or fusion prototypes are actually loaded at runtime. At runtime neos collects all the files and "constructs" the effective nodetype configuration by plugging together the yaml or fusion, overriding keys depending on package loading order and so on.
It is hard to keep track, what is actually happening.
I'm dreaming of a feature that shows me the effective configuration when hovering over a nodetype or fusion prototype.
As there is a backend view for all of this (which is far away for me while I'm developing from IntelliJ) I assume that this could be generated by periodically running the flow binary via the plugin or something (e.g. when triggering a save)?
Would even be cooler to add something like git blame to that view that shows where a certain key's value comes from (which file or package), to track down problems when overriding keys in fusion or nodetype definitions.
The text was updated successfully, but these errors were encountered: