Skip to content
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

Restrict mobx to <6.13.0 #7315

Merged
merged 1 commit into from
Nov 21, 2024
Merged

Conversation

pjonsson
Copy link
Contributor

What this PR does

Mobx 6.13 makes tsc error out with:

Error: node_modules/mobx/dist/types/observableset.d.ts(45,31): error TS2552: Cannot find name 'ReadonlySetLike'. Did you mean 'ReadonlySet'?

which is issue 3903 in the mobx repository.
Restrict mobx to <6.13 for now to avoid
the issue.

Test me

I believe this is tested by CI.

Checklist

  • There are unit tests to verify my changes are correct or unit tests aren't applicable (if so, write quick reason why unit tests don't exist)
  • I've updated relevant documentation in doc/.
  • I've updated CHANGES.md with what I changed.
  • I've provided instructions in the PR description on how to test this PR.

Copy link
Collaborator

@na9da na9da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @pjonsson, could you please amend the CHANGES file and sync with current main please?

CHANGES.md Outdated Show resolved Hide resolved
Mobx 6.13 makes tsc error out with:

Error: node_modules/mobx/dist/types/observableset.d.ts(45,31): error TS2552: Cannot find name 'ReadonlySetLike'. Did you mean 'ReadonlySet'?

which is issue 3903 in the mobx repository.
Restrict mobx to <6.13 for now to avoid
the issue.
@na9da na9da merged commit ffbba71 into TerriaJS:main Nov 21, 2024
6 checks passed
@pjonsson pjonsson deleted the restrict-mobx-version branch November 21, 2024 23:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants