feat: Rename column "Update To" to "Latest" in remediation advice table #295
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.
Description:
This PR updates the column name in the
addRemediationAdviceTableRows
function fromUpdate To
toLatest
for improved clarity and alignment with the backend data.Why this change?
The term
Update To
could be misleading as it doesn't precisely represent the data provided by the backend. By renaming it toLatest
, the table becomes clearer and more specific for users.For more context, refer to the discussion in the related issue: #292 - Unexpected Behavior When Scanning Non-Existing and Latest Versions of npm Packages.