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

ViewPropTypes.style is not defined #115

Open
aniul opened this issue Aug 23, 2024 · 4 comments
Open

ViewPropTypes.style is not defined #115

aniul opened this issue Aug 23, 2024 · 4 comments

Comments

@aniul
Copy link

aniul commented Aug 23, 2024

Hi! 👋

Firstly, thanks for your work on this project! 🙂

Today I used patch-package to patch [email protected] for the project I'm working on.

Here is the diff that solved my problem:

diff --git a/node_modules/react-native-smooth-pincode-input/src/index.js b/node_modules/react-native-smooth-pincode-input/src/index.js
index 0a00f22..5fc4ac3 100644
--- a/node_modules/react-native-smooth-pincode-input/src/index.js
+++ b/node_modules/react-native-smooth-pincode-input/src/index.js
@@ -6,8 +6,8 @@ import {
   TextInput,
   StyleSheet,
   I18nManager,
-  ViewPropTypes,
 } from 'react-native';
+import { ViewPropTypes } from 'deprecated-react-native-prop-types';
 import * as Animatable from 'react-native-animatable';
 
 const styles = StyleSheet.create({

This issue body was partially generated by patch-package.

@jsproull
Copy link

This PR was opened last year and should address this issue: 106. Any chance we could get that merged and a new version published?

@ddtch
Copy link

ddtch commented Sep 27, 2024

Yes it would be nice if someone can merge it please

@mic-automed
Copy link

I just tried using this package and this issue immediately broke my app. Considering there is already a fix that is awaiting a merge FROM OVER A YEAR AGO, is there any chance this will be fixed any time soon?

In the mean time I will look for some other solution....

@CalvinNFT
Copy link

I just tried using this package and this issue immediately broke my app. Considering there is already a fix that is awaiting a merge FROM OVER A YEAR AGO, is there any chance this will be fixed any time soon?

In the mean time I will look for some other solution....

Found an alternative?

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