-
Notifications
You must be signed in to change notification settings - Fork 14
MIG-105: Removed the work around function #373
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
Conversation
@@ -147,7 +147,7 @@ class StudyManifestTools { | |||
this.writeIssues(removedEntities) | |||
this.writePackage('study', extraConfig) | |||
|
|||
return { manifest, removedEntities } | |||
return { manifest, removedEntities, mappingScript } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi Sharad, this is unrelated to MIG-105, this is already addressed in Davide's PR
This ticket is about removing the workaround in MenuConfigMapping class
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also I'd like to understand why we get package-lock.json changes, can you confirm these are expected changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good
@@ -147,7 +147,7 @@ class StudyManifestTools { | |||
this.writeIssues(removedEntities) | |||
this.writePackage('study', extraConfig) | |||
|
|||
return { manifest, removedEntities } | |||
return { manifest, removedEntities, mappingScript } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also I'd like to understand why we get package-lock.json changes, can you confirm these are expected changes?
In this PR, i removed the Work around function