Skip to content
This repository was archived by the owner on Sep 6, 2021. It is now read-only.

update codemirror to 5.24.0 #13116

Merged
merged 13 commits into from
Feb 28, 2017
Merged

update codemirror to 5.24.0 #13116

merged 13 commits into from
Feb 28, 2017

Conversation

zaggino
Copy link
Contributor

@zaggino zaggino commented Feb 20, 2017

contains various TypeScript improvements (among others) that I'd like to see in master since this upgrade is not doable through an extension

cc @ficristo @petetnt @swmitra

@swmitra
Copy link
Collaborator

swmitra commented Feb 21, 2017

This upgrade bring quite a few bug fixes accumulated through 22, 23 and 24. I would also like to see use of sticky prop in position. Good upgrade for Brackets 1.9 👍

@swmitra swmitra added this to the Release 1.9 milestone Feb 21, 2017
@ficristo
Copy link
Collaborator

This breaks a lot of tests. You need to change them to consider the new sticky property.

@swmitra
Copy link
Collaborator

swmitra commented Feb 21, 2017

Yes @ficristo. For now to leverage on the bug fixes and mode optimizations we can just upgrade the CM version, but to actually use the new features we need a complete development cycle which we can't have for Brackets 1.9. Do let us know if you think that this upgrade alone might cause problems.

@ficristo
Copy link
Collaborator

For what I looked we only need to adjust our tests.
This only mean that before we checked for {line: x: ch:y} now we need to check for {line: x: ch:y, sticky: null}. We don't use new features.
Hopefully this is the only change for all breaking tests.

@zaggino
Copy link
Contributor Author

zaggino commented Feb 22, 2017

I believe I have resolved test issues, can you please re-check guys?

Copy link
Collaborator

@swmitra swmitra left a comment

Choose a reason for hiding this comment

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

I am OK with the test changes. This will reduce our work a lot if position object changes again in future.

@swmitra
Copy link
Collaborator

swmitra commented Feb 22, 2017

Restarted the travis build and all checks are successful. Waiting for @ficristo to approve this PR and we can merge then.

@ficristo
Copy link
Collaborator

There were still some failures on extensions tests.
(There were other failures but probably related to my system)

@ficristo
Copy link
Collaborator

I just noticed 5.24.2 was released. Better upgrade to it.

@zaggino
Copy link
Contributor Author

zaggino commented Feb 23, 2017

Upgraded to 5.24.2, sadly something is not right with unit testing on my machine. Some tests do randomly pass and fail and then I try to open developer tools to debug, the whole testing window just freezes, quite terrible development experience.

@swmitra
Copy link
Collaborator

swmitra commented Feb 23, 2017

I will also try to see if I can run the tests and figure out any particular issue @zaggino.

@zaggino
Copy link
Contributor Author

zaggino commented Feb 23, 2017

thanks, yesterday all integration tests were passing with this PR and now they are randomly failing, drives me mad but i'll give it a try again probably tomorrow

@zaggino
Copy link
Contributor Author

zaggino commented Feb 25, 2017

fixed (hopefully all) extension unit tests, @ficristo can you please have a look and let me know which (if any) particular tests still fail because of this PR?

@ficristo
Copy link
Collaborator

It seems there are still some failures with Extensions \ JavaScript Code Hinting and Extensions \ JSQuickEdit.
NOTE: I reverted 7883b01 before testing. See #13126

@zaggino
Copy link
Contributor Author

zaggino commented Feb 28, 2017

@ficristo fixed those tests, also added a fix for #13126 - 1de6b88?w=1

@ficristo
Copy link
Collaborator

Thank you for all the effort.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants