PJS001 conversion based units (IVS-680) #471
Conversation
(IVS-680)
aothms
left a comment
aothms
left a comment
There was a problem hiding this comment.
Really nice, but have a look at the two scenario suggestions. I think the schema still allows for some situations we need to check.
| if 'npath' in inspect.getargs(fn.__code__).args: | ||
| kwargs = kwargs | {'npath': current_path} | ||
| top_level_index = current_path[0] if current_path else None | ||
| max_index = len(current_path) - 1 |
There was a problem hiding this comment.
⚠
This is exactly related to my comment on #468
We should not be doing this, because in this way we're linking the wrong instance to the outcome presentation. We just really should make sure that the stack of values we build forms a proper tree.
There was a problem hiding this comment.
Something needs to be done because this feature file generates an IndexError as-is. The code tries to access element at index 1 when there is a single value in the list. I'll review your comment for clues. Maybe the Given statement needs to be revised.
There was a problem hiding this comment.
Ok, the IndexError makes sense in #468 based on the Given statement. I'm working through that now & will use lessons learned to resolve this PR.
Co-authored-by: Thomas Krijnen <[email protected]>
Co-authored-by: Thomas Krijnen <[email protected]>
Co-authored-by: Thomas Krijnen <[email protected]>
…units' into IVS-680-PJS001-conversion-based-units
(IVS-680)
(IVS-680)
(IVS-680)
closes #107