Skip to content

Conversation

@NickLaurenson-Visionick
Copy link

@NickLaurenson-Visionick NickLaurenson-Visionick commented Jan 16, 2026

Hello, this PR aim to fix #278.

As mention in the issue, the root caused came from get_dynamic_mapped_parameter_names, not return the full nested path:
if the the field to be mapped was .nested_field.final_field, the function return final_field causing error in the generated code.

Regarding the test, I wrote some basic one, let me know if need to do something else

@NickLaurenson-Visionick NickLaurenson-Visionick force-pushed the fix/278 branch 2 times, most recently from 475084b to 1664af6 Compare January 16, 2026 10:23
Nick Laurenson added 2 commits January 16, 2026 11:28
- Add nested_map_keys.yaml: test YAML with nested struct and __map_ parameter
- Add nested_map_test.yaml: test YAML for basic nested map parsing
- Add test_parse_nested_map_keys: test that nested map YAMLs parse correctly
- Add test_get_dynamic_mapped_parameter_nested: unit test for function output
- Update setup.py to install new test files
The old implementation only returned the key names without the parent
struct path prefix. This caused generated code to reference non-existent
members like 'updated_params.entries' instead of 'updated_params.nested.entries'.

Changes:
- Rename old get_dynamic_mapped_parameter to get_dynamic_mapped_parameter_names
- Create new get_dynamic_mapped_parameter that builds full paths including
  parent struct prefixes (e.g., 'nested.entries' instead of just 'entries')
- Update get_dynamic_parameter_map to use the renamed function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No way to reference non top-level keys in parameters map

1 participant