feat: map privilege-apply business errors in dms-kit - #893
Open
LordofAvernus wants to merge 1 commit into
Open
Conversation
Coverage report
Test suite run success3776 tests passing in 826 suites. Report generated by 🧪jest coverage report action from 2ffb21a |
Surface no-assignee, duplicate-open and invalid account name from provision using the shared error mapper.
LordofAvernus
force-pushed
the
dms-ui/feat-982
branch
from
September 10, 2026 03:29
0fba460 to
2ffb21a
Compare
LordofAvernus
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Problem
CE and EE UIs share dms-kit error mapping. These messages must land on
dms-uimainand reachmain-eethrough Sync, not through an EE-only feature PR.Test plan
privilege_apply.duplicate_openandprivilege_apply.invalid_account_namemap to the expected messagesFixes actiontech/dms-ee#982