Uh oh!
There was an error while loading. Please reload this page.
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.
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.
This test verifies the
handleProjectStatuscontract (emptytargetNamewhen no targets are configured), but the code change in this PR is on the runtime-status path that callshandleRuntimeLookup. So the test doesn't actually exercise the render line you modified.It's a fine regression guard for the default-path fix that landed in #1068, but if the goal is to lock in the behavior that this PR changes, consider adding a test for
handleRuntimeLookupor a rendering test for the runtime-status header — otherwise nothing in the test suite prevents a future regression of line 113–114.Also, minor: this test is inside
describe('handleProjectStatus — live enrichment', ...)but has nothing to do with live enrichment. Consider moving it to a more appropriate describe block (e.g. the existinghandleProjectStatusblock that covers target resolution).