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

Proptypes issues with new RN 48 #61

Open
mmaschenko opened this issue Sep 20, 2017 · 6 comments
Open

Proptypes issues with new RN 48 #61

mmaschenko opened this issue Sep 20, 2017 · 6 comments

Comments

@mmaschenko
Copy link

After i upgraded react native to last version, react-native-keyboard-spacer started to crash application because after react changes Proptypes is now can not be imported from react directly. You need install another package as described here https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html. I was able to fix it by changing package files directly, but it is bad idea for a lot of reasons

@hmziqrs
Copy link

hmziqrs commented Sep 21, 2017

fixed this issue by editing KeyboardSpacer.js

import React, { Component } from 'react'; import PropTypes from 'prop-types';

@WillyRamirez
Copy link

WillyRamirez commented Sep 22, 2017

@hackerhgl Thnx, worked.
PR tho?

@hmziqrs
Copy link

hmziqrs commented Sep 26, 2017

@WillyRamirez They are too lazy to do accept a simple PR

#58

@WillyRamirez
Copy link

@hackerhgl yeah i saw, OP is no longer supporting this package. Luckily it's just one file, i took it out and added it to my own components folder. Alternatively we could fork it, merge all PR

@NachtRitter
Copy link

@Andr3wHur5t please merge PRs and make new release. If you don't want to maintance this repo, just give rights to someone else.

@Andr3wHur5t
Copy link
Owner

I apologize if my response time is slow.

Every PR is tested with multiple versions of react native to see what minimal supported version is to consider all the apps which use this that haven’t upgraded; breaking existing apps rather than upgraded ones (which haven’t released) would be bad also.

I would love to have automated tests to streamline this process but it has proven difficult with the feature support (such as hardware keyboards). As such I do manual testing which takes time.

As for adding another maintainer I’m open to this assuming they consider down stream consequences (requests welcome); but as of yet no one has offered.

I’ve recently pushed a out which works on the most recent version of RN. If you are still seeing this issue please post a repro so I can verify.

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

No branches or pull requests

5 participants