Skip to content
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

[DAT-16135] add new scope flag for modifyChangeSet flow #5707

Merged
merged 5 commits into from Mar 22, 2024

Conversation

KushnirykOleh
Copy link
Contributor

@KushnirykOleh KushnirykOleh commented Mar 18, 2024

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)

Description

For some parsers, (like mongosh parsers) we need to know when modifyChangeSet flow is happening, as we can't run mongo instructions without native executor so runWith is required. But in modifyChangeSet flow runWith is added to the changeset later on, after parsing.
Adding modifyChangeSets flag to the Scope allows parsers to read it and skip runWith validation knowing it's inner changeset and it gets 'runWith' attribute later.

Copy link
Contributor

@wwillard7800 wwillard7800 left a comment

Choose a reason for hiding this comment

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

Looks good. This might be a place for a short comment where you added the scope to state where the flag that you added will be used.

@KushnirykOleh KushnirykOleh marked this pull request as ready for review March 18, 2024 17:31
@KushnirykOleh KushnirykOleh changed the title [DAT-16135] WIP add new scope for modifyChangeSet flow [DAT-16135] add new scope flag for modifyChangeSet flow Mar 18, 2024
@filipelautert filipelautert added this to the 1NEXT milestone Mar 22, 2024
@filipelautert filipelautert merged commit d224b5b into master Mar 22, 2024
33 of 34 checks passed
@filipelautert filipelautert deleted the DAT-16135 branch March 22, 2024 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

5 participants