fix issue if glob_params is not int #48
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is needed to parse includes like: `Contracts: !include ["contracts/*.yaml", "Contracts"]` where the last string is not of any further meaning
maurerle
added a commit
to assume-framework/assume
that referenced
this pull request
Sep 11, 2024
maurerle
added a commit
to assume-framework/assume
that referenced
this pull request
Sep 11, 2024
tanbro
pushed a commit
that referenced
this pull request
Sep 22, 2024
|
Thanks for the PR! Codes of the PR picked in commit da96563 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I want to parse the yaml files from the AMIRIS examples repository:
https://gitlab.com/dlr-ve/esy/amiris/examples/-/blob/v2.1.0/Germany2019/scenario.yaml?ref_type=tags#L503
We have an include like this in there:
Contracts: !include ["contracts/*.yaml", "Contracts"]where the last string is not of any further meaning - I can not change these files either.
Currently, this gives a ValueError as it is tried to be read as an integer.
I can confirm that this was working in the 1.x version?
So it would be very cool to have this workaround included! :)