Skip to content

Fix to resolve env in key before merging #874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 20, 2021
Merged

Fix to resolve env in key before merging #874

merged 3 commits into from
Apr 20, 2021

Conversation

jshum2479
Copy link
Member

This fix is for JIRA WDT 552 - resolving the key in the model with @@env notation before merging the models to avoid having duplicate copies of the same key element in the model resulting wrong domain created.

@jshum2479 jshum2479 requested review from ddsharpe and rakillen April 19, 2021 21:15
@@ -305,6 +305,7 @@ def merge_model_files(model_file_value, variable_map=None):
It may be a single file, or a comma-separated list of files.
:param variable_map: variables to be used for name resolution, or None
:param model_file_value: the value specified as a command argument
;param model_context: model context
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like a semi-colon here instead of a colon

Copy link
Member

@rakillen rakillen Apr 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

model_context isn't an argument any more, can be removed

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@ddsharpe ddsharpe merged commit 87d5c39 into master Apr 20, 2021
@ddsharpe ddsharpe deleted the fixenvmerge branch April 20, 2021 20:37
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.

3 participants