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

fix qs 6.5.x and add qs 6.9.x #3631

Merged
merged 2 commits into from
Nov 14, 2019

Conversation

LoganBarnett
Copy link
Contributor

Other notes:

The qs libdefs used the only Function, Object, and sometimes any types - some of which cause issues in newer versions of Flow and/or flow-typed. The old qs 6.5.x tests have had the bare minimum done to get the tests passing again. Most of the work was done against a new (copied) set of libdefs for 6.9.x. I did not know what versions added which arguments, or if certain arguments were omitted on the original 6.5.x, and perusing the documentation for qs did not reveal this in a timely manner. It seemed to make sense make a clean break to 6.9.x. The 6.9.x
version of qs should be entirely backwards compatible with 6.5.x, since only new, optional arguments have been added.

The qs libdefs used the only Function, Object, and sometimes any types - some of
which cause issues in newer versions of Flow and/or flow-typed. The old qs 6.5.x
tests have had the bare minimum done to get the tests passing again. Most of the
work was done against a new (copied) set of libdefs for 6.9.x. I did not know
what versions added which arguments, or if certain arguments were omitted on the
original 6.5.x, and perusing the documentation for qs did not reveal this in a
timely manner. It seemed to make sense make a clean break to 6.9.x. The 6.9.x
version of qs should be entirely backwards compatible with 6.5.x, since only
new, optional arguments have been added.
@LoganBarnett
Copy link
Contributor Author

I am happy to appease the lintings we have re: no-implicit-inexact, but these lintings do not run locally which makes iterating on this both slow and tedious. Is there something I can do to see these errors in my local environment?

@AndrewSouthpaw
Copy link
Contributor

Hm. Does running travis.sh work for you?

Copy link
Contributor

@AndrewSouthpaw AndrewSouthpaw left a comment

Choose a reason for hiding this comment

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

LGTM.

@LoganBarnett
Copy link
Contributor Author

./travis.sh does work for me and gives me the same errors. I'll have a fix shortly. Thanks!

@LoganBarnett
Copy link
Contributor Author

@AndrewSouthpaw fixed!

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.

None yet

2 participants