Fix Issue #2589 TypeError When There Are No Nested Requirements #2590
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
dbluhm
approved these changes
Nov 3, 2023
Signed-off-by: Robert Simpson <RobS.git9@MailScreen.com>
dbluhm
force-pushed
the
fix/TypeError_when_no_nested_requirements
branch
from
4366643
to
abd79bb
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
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.
Added
ifstatement, same as in calling functioncreate_vp, to the called functionapply_requirements. Since the former callsapply_requirementsin both cases (if req.nested_reqor not), the called function should handle both cases as well.