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 attempting to pass data to nuemark tags via attribute bindings (e.g :data="my_data"), the entire attribute string is treated as a single string key, preventing the use of nested data from the site/application YAML files.
This prevents a natural structuring of data within the site.yaml files, and given there is no built-in way to load application data from any other source, creates issues with name pollution/collision with Nue-reserved keys inside the site.yaml file.
...you could also just split the key by '.' and recursively descend into the object, but if this code isn't executed at runtime and you're not worried about injection attacks then the eval method would allow for array access as well I suppose. It would need better documentation though to communicate the flexibility of the eval method.
Describe the Bug
When attempting to pass data to nuemark tags via attribute bindings (e.g
:data="my_data"
), the entire attribute string is treated as a single string key, preventing the use of nested data from the site/application YAML files.This prevents a natural structuring of data within the
site.yaml
files, and given there is no built-in way to load application data from any other source, creates issues with name pollution/collision with Nue-reserved keys inside the site.yaml file.Environment
OS: Linux
Nuekit: 1.0.0-RC3
Minimal Reproduction
The text was updated successfully, but these errors were encountered: