This patch changes the behaviour of the parseParamRef function. First it grabs the "Parameters" field. Then it iterates over the child fields (which are parameter definitions) and it returns as soon as it finds one which matches the name in the path.
I noticed that the path is still flagged as invalid if the parameter reference is added after the path is set but it works the other way round (adding the parameter then changing the path) so I think there's somewhere else I need to tweak too but I'm not sure where it is. Any pointers would be really appreciated!
Great project - thanks!
This is a partial fix for #354.
Steps to repro the issue:
getValue()
onundefined
)Alternatively, just use this spec.
This patch changes the behaviour of the
parseParamRef
function. First it grabs the "Parameters" field. Then it iterates over the child fields (which are parameter definitions) and it returns as soon as it finds one which matches the name in the path.I noticed that the path is still flagged as invalid if the parameter reference is added after the path is set but it works the other way round (adding the parameter then changing the path) so I think there's somewhere else I need to tweak too but I'm not sure where it is. Any pointers would be really appreciated!