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

Migrate to flatlist #65

Merged

Conversation

kesha-antonov
Copy link
Contributor

No description provided.

@theneva
Copy link
Contributor

theneva commented Apr 8, 2019

Hi! I've sent a PR to the fork that should make the build pass (kesha-antonov#1). It:

  • Fixes the linting errors
  • Downgrades React to ~15.5.4 (which is still an upgrade from 15.4.0-rc.4)
  • Makes the keyExtractor prop optional, as it's also okay to pass a key to each item in renderItem

I'm pretty sure the examples need to be updated before this can land, though.

@theneva theneva mentioned this pull request Apr 8, 2019
@kesha-antonov
Copy link
Contributor Author

Hey! @theneva Merged

@Javier-Rotelli
Copy link
Collaborator

Great! i'm going to merge this.
@theneva what was the problem you had that you had to downgrade react?

@Javier-Rotelli Javier-Rotelli merged commit ee99242 into byteburgers:master Apr 8, 2019
@theneva
Copy link
Contributor

theneva commented Apr 9, 2019

Awesome, thank you!

@Javier-Rotelli the issue is that react-native-mock imports proptypes directly off react, instead of from the prop-types package. That export disappeared from React in 15.6.

15.5 logs warnings during tests but doesn't break.

react-native-mock is unmaintained and it wasn't super easy to get rid of it (I tried replacing mocha with jest to use its built-in mocking, but didn't try mockery which might be worth a look RealOrangeOne/react-native-mock#139 (comment)).

@theneva
Copy link
Contributor

theneva commented Apr 9, 2019

Oh btw @Javier-Rotelli it might be obvious but it hasn't been mentioned explicitly: the change to renderItem makes this a breaking change so it has to be released as a major. Is there anything preventing a release of this?

@Javier-Rotelli
Copy link
Collaborator

@theneva not really, other than the time i needed to check if there were breaking changes or not.
i'll make the release and put up issues regarding prop-types and react-native-mock.

@theneva
Copy link
Contributor

theneva commented Apr 11, 2019

@Javier-Rotelli thank you very much! However, it seems like the actual publish to npm didn't go through (and it doesn't look like you're a collaborator on the package). If @mrlaessig gives you the right permissions, will you please try publishing it again? 😄

@Javier-Rotelli
Copy link
Collaborator

yup, i need @mrlaessig 's permissions to publish

@mrlaessig
Copy link
Collaborator

Hey @Javier-Rotelli what it you npm username?

@Javier-Rotelli
Copy link
Collaborator

@mrlaessig -> javierrotelli

@mrlaessig
Copy link
Collaborator

@Javier-Rotelli You now should have the permission to do a release on npm ;)

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.

4 participants