Open GabrielBB opened 7 years ago
Hey @GabrielBB I made a pull request today that goes through fixing the error you are seeing. React switched over to a different package called prop-types and that breaks it if you have a newer version.
Did this get solved?
@ccostel I made a PR for it but i don't think it was merged yet.
@hans0low I actually implemented your changes and they work. Hopefully @MichaelCereda will soon merge it. Thanks for the PR :) 👍
Still undefined is not an object (evaluating '_react3.default.PropTypes.string'). Did you update repo?
Yeah, I also had to apply the changes of the PR manually, But it works. Thanks @hans0low
@ccostel @hans0low is there a way of applying the PR automatically while waiting for the merge to happen? i tried suggestions here but kept running into errors.
@aanchan
npm install MichaelCereda/react-native-form-generator#pull/124/head
I believe this should work.
It's been a while and @MichaelCereda still did not merge. I tweeted him in the hope that it will come to his attention.
Hi,
I'm getting error. I tried npm install MichaelCereda/react-native-form-generator#pull/124/head but I'll receiveing the following message:
npm ERR! code 1 npm ERR! Command failed: /usr/bin/git checkout pull/124/head npm ERR! error: pathspec 'pull/124/head' did not match any file(s) known to git.
I'm trting to run this using Expo. Can this be the problem ?
I ask for help on this issue.
@ventocilla You might want to try manually changing the files.
As of now, the @hans0low PR has been merged. But I installed the package today, then got the "undefined is not an object (evaluating '_react3.default.PropTypes.string')" error. I took a look at the .js files that the @hans0low PR (#124) changed but my local files (that I installed today), did not have the @hans0low PR changes applied. To fix the error, I had to manually edit my local .js files to match the @hans0low PR. #
I just installed the package today, I got this error which appears only if I only do:
import { Form } from 'react-native-form-generator'
@hopewise did you manage to fix it?
no, I abandoned using this package..
I just copy the example code on the README.md and it throws this error. I think it's because something about PropTypes has changed in newer versions of React Native.