test: Add overlayId to duplicate error message #183
Merged
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
Updated test code to match the actual implementation where the duplicate overlayId error message now includes the actual ID value.
The test was failing because it expected the old error message format while the implementation was outputting an improved message with the overlayId included.
Related Issue: Fixes # (issue_number)
Changes
packages/src/event.test.tsx"You can't open the multiple overlays with the same overlayId. Please set a different id.""You can't open the multiple overlays with the same overlayId(same-overlay-id). Please set a different id."Motivation and Context
The actual implementation code was enhanced to include the overlayId value in duplicate overlay error messages for better debugging experience.
However, the test code was still expecting the old message format, causing test failures. This change fixes the mismatch between test expectations and actual implementation behavior.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist
Further Comments
This is a test fix to align test expectations with the improved error messaging in the actual implementation.
No functional changes are involved, only ensuring test stability and accuracy.