Ntrfcs 207 #303
Merged
Ntrfcs 207 #303
+24
−1
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
SrujanaSaka20
requested review from
tevo-nikita-ivashkov,
bsl782,
harmantevo,
vmc123,
someshravula2507 and
vl-santoshkumaralli
bsl782
approved these changes
Jan 24, 2025
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.
Jira: NTRFCS-207
Important
Toggle to Squash and Merge when merging PRs to
stagingbranchWhat
This PR adds/removes/fixes…
Added openLegendInitially flag
Testing
I tested this code by (unit/integration/manual) testing…
Extras
bin/build,.envchanges etc.(if any are checked, please describe below)
PR Code Coverage
Measure with
bin/test_covor some other means. You can find html coverage levels incoverage/index.htmlor instdout.After a successful test run, you can also see calculated and merged coverage, per branch, on Grafana