-
Notifications
You must be signed in to change notification settings - Fork 36
test(fit): assert mxGraphView calls in the fit integration tests #3527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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.
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.
Thanks, but this is a false positive for the test data, so I'll keep the table as is.
it.eachhere uses a tagged template literal. Unlike a plain template string, a tagged template does not coerce its interpolated expressions: Jest'seachreceives the raw values and passes them to the test unchanged. Themargincell is therefore the actualundefined, not the string"undefined".Proof from the suite itself:
marginreachesensurePositiveValue, i.e.Math.max(input ?? 0, 0). With a realundefinedthis returns0, which is exactly why the${undefined}rows assert the no-margin results (4.78/5.72/8at translate-70, 60). If the value were the string"undefined", the expression would beMath.max(NaN, 0)→NaN, the computed scale would beNaN, and those assertions would fail. They pass, so the value is genuinelyundefined.The only
undefined → stringconversion happens in the generated test name ($margin→ "undefined"), which is intentional: it documents the no-margin case and distinguishes those rows from themargin: 30/margin: 100ones. The suggestion on line 142 correctly identifies the title as the sole conversion path; the suggestions on lines 139-141 assume the data itself is converted, which it isn't.On the proposed workarounds: each trades readability for silencing a rule that misfires on tagged-template semantics.
${null}would also change the documented input (and the Zoom table already interpolates${null}/${undefined}on purpose). So I'll resolve this as a false positive rather than change the code.