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
A problem has been identified with Mantine v6 library that is impacting snapshot testing. When attempting to match the snapshot, it is observed that the snapshot keeps changing with each update, making it challenging to perform reliable tests. This issue was not present in the previous version, Mantine v5.
Based on the available information, it appears that the issue may be related to the class hash generator (as shown below). However, further investigation is necessary to confirm this hypothesis and identify the root cause of the problem.
What version of @mantine/hooks page do you have in package.json?
6.0.0
If possible, please include a link to a codesandbox with the reproduced problem
No response
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Possible fix
No response
The text was updated successfully, but these errors were encountered:
What package has an issue
@mantine/core
Describe the bug
A problem has been identified with Mantine v6 library that is impacting snapshot testing. When attempting to match the snapshot, it is observed that the snapshot keeps changing with each update, making it challenging to perform reliable tests. This issue was not present in the previous version, Mantine v5.
Based on the available information, it appears that the issue may be related to the class hash generator (as shown below). However, further investigation is necessary to confirm this hypothesis and identify the root cause of the problem.
What version of @mantine/hooks page do you have in package.json?
6.0.0
If possible, please include a link to a codesandbox with the reproduced problem
No response
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Possible fix
No response
The text was updated successfully, but these errors were encountered: