Sm/nuts fix because topics changed #330
Merged
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
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.
What does this PR do?
previously, the NUT used
deployas the top level topic. The plugin code caught that because there was a top-leveldeploycommand.We recently hid that command (been deprecated for a while) and so I changed the NUT to use
project. That exposed a bug where the code didn't catch the existence of commands underprojectand mark it as external. yay, NUTs.This fixes the logic and adds some robust UT to the method that calculates the topics.
What issues does this PR fix or reference?
@W-13525630@
failure example: https://github.com/salesforcecli/cli/actions/runs/5151301567