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

WIP: MobX 5 #1380

Closed
wants to merge 197 commits into from
Closed

WIP: MobX 5 #1380

wants to merge 197 commits into from

Conversation

mweststrate
Copy link
Member

@mweststrate mweststrate commented Mar 8, 2018

Nothing to see here yet

  • proxy array
  • proxy object
  • ObservableMap extends Map Not supported by TS / babel
  • disable spy and other dev features in production builds? (for smaller build)
  • remove deprecated api's
  • optimize reportObserved recording using sets?
  • release mobx 5 which always throws: pick mobx 4 or 15 Meh. Just mobx 5 should be fine
  • process all open todos
  • introduce seal option? proxy: false is a new option instead
  • Polish changelog
  • Update documentation
  • Bump peer deeps in (should be completely backward compatable)

@mweststrate mweststrate changed the base branch from master to mobx4 March 8, 2018 16:27
@mweststrate mweststrate mentioned this pull request Mar 10, 2018
@mweststrate mweststrate mentioned this pull request Mar 12, 2018
@@ -16,6 +16,12 @@
*
*/

if (typeof Proxy === "undefined") {
throw new Error(
Copy link
Member

Choose a reason for hiding this comment

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

🎉

package.json Outdated
@@ -1,6 +1,6 @@
{
"name": "mobx",
"version": "4.0.0-beta.4",
"version": "15.0.0-alpha.1",
Copy link

@tkrotoff tkrotoff Mar 12, 2018

Choose a reason for hiding this comment

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

Do you mean "5.0.0-alpha.1"?

Copy link
Member Author

Choose a reason for hiding this comment

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

Actually might be 15 :-) .Completely in the spirit of React.

But more importantly, I want to keep supporting MobX 4 for those we have to support browsers without proxies. And calling this one 5 would hamper the ability to make breaking changes on the "4-branch"

Copy link
Member

Choose a reason for hiding this comment

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

hmhm. Major is the new minor

Copy link
Member

Choose a reason for hiding this comment

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

I mean i have no objection, it's just a bit mind bending ^^

@mweststrate
Copy link
Member Author

mweststrate commented Jun 4, 2018 via email

@mweststrate
Copy link
Member Author

mweststrate commented Jun 5, 2018

  • Fix binding of computed properties

CHANGELOG.md Outdated

### Known Issues

* Jest `toEqual` might throw an error `allKeys[x].match is not a function` when trying to equal observable arrays. This is a bug in Jest [report](https://github.com/facebook/jest/issues/6391). The simple work around for now is to slice (or `toJS` if the problem is recursive) the array first.
Copy link
Member

Choose a reason for hiding this comment

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

This was merged into jest - so update to "older versions of jest"?

Copy link
Member Author

Choose a reason for hiding this comment

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

Added a note

CHANGELOG.md Outdated
### Known Issues

* Jest `toEqual` might throw an error `allKeys[x].match is not a function` when trying to equal observable arrays. This is a bug in Jest [report](https://github.com/facebook/jest/issues/6391). The simple work around for now is to slice (or `toJS` if the problem is recursive) the array first.
* Jest `toEqual` matcher might no longer corretly equal your class instances, complaining about differences in the MobX adminstration. This is due to a bug with the processing of symbols: [report](https://github.com/facebook/jest/issues/6392). For now you might want to use a custom matcher if you are directly equalling observable objects. As a work around `toJS(object)` could be used before diffing.
Copy link
Member

Choose a reason for hiding this comment

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

Also fixed I think?

Copy link
Member Author

Choose a reason for hiding this comment

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

Same

@mweststrate
Copy link
Member Author

Released!

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.