You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow column mapping when a check reports a critical missing reference issue, alongside the existing missing column and missing-field exceptions.
Users must still meet the existing mapping criteria, including having unassigned columns. Other critical external issues continue to block mapping. Missing references remain critical on the Check results page.
Regression tests cover critical missing reference issues, the spare-column requirement, and blocking by other critical external issues.
[optional] Are there any post deployment tasks we need to perform?
None.
[optional] Are there any dependencies on other PRs or Work?
None.
Summary by CodeRabbit
Bug Fixes
Column mapping is no longer blocked by a missing reference issue alone. Mapping eligibility still depends on having a spare column and no other blocking critical issue.
No actionable comments were generated in the recent review. 🎉
ℹ️ Recent review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: 6c971202-fca6-4e6f-91fb-e93431c7021c
📥 Commits
Reviewing files that changed from the base of the PR and between 7e1fac2 and fc79aa8.
📒 Files selected for processing (2)
src/services/columnMappingDecider.js
test/unit/statusController.test.js
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
Walkthrough
The column mapping decision now treats missing reference issues as non-blocking. Tests cover mapping eligibility when a spare column is available and when other blocking conditions are present.
The blocking-issue filter now exempts missing reference issues, alongside missing column and missing-field. The comment also identifies missing reference as fixable by column mapping.
Test mapping eligibility test/unit/statusController.test.js
Tests cover missing reference as a non-blocking issue. Additional cases check that mapping requires a spare column and is not offered when another critical external issue exists.
The change allows eligible users to try column mapping without bypassing the existing blockers. If the subsequent check still reports a critical missing-reference issue, it remains visible as an issue that must be fixed.
Pre-merge checks · 5
Passed checks (5 passed)
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly summarises the main change: allowing column mapping for critical missing reference issues.
Linked Issues check
The change for #1294 adds missing reference to the non-blocking issue types in hasBlockingNonColumnMappingTasks. The existing eligibility logic remains active. Tests cover an available spare colum…
Out of Scope Changes check
The changes are limited to the column-mapping decision rule, its explanatory comment, and regression tests. Each change supports #1294 or verifies the stated mapping conditions. No unrelated productio…
Docstring Coverage
Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
Commit to this branch
Create a new PR
📝 Generate docstrings
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the mapping gate, A missing reference need not wait. With spare columns in the row, The mapping path can now show. If other critical issues appear, The rabbit knows the block is clear.
Comment @coderabbitai help to get the list of available commands.
This file contains hidden or 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
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 type of PR is this? (check all applicable)
Description
Allow column mapping when a check reports a critical
missing referenceissue, alongside the existingmissing columnandmissing-fieldexceptions.Users must still meet the existing mapping criteria, including having unassigned columns. Other critical external issues continue to block mapping. Missing references remain critical on the Check results page.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Added/updated tests?
Regression tests cover critical
missing referenceissues, the spare-column requirement, and blocking by other critical external issues.[optional] Are there any post deployment tasks we need to perform?
None.
[optional] Are there any dependencies on other PRs or Work?
None.
Summary by CodeRabbit