You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for sharing the information.
We are cautious about changing specifications because we must consider the impact on other customers already using our SDK.
I will look into a mono repo.
Please let us know if you have any reasons why we should, such as background, impact, effects, opinions, etc.
Thank you for always using our products and solutions.
I don't know if I have an argument about whether or not to use monorepo. To be honest, in my tech team, we'd like to get away from this "monorepo" pattern/arch. But many react native packages have this monorepo support, it's become a common thing today.
After internal discussions about the monorepo, we would like to improve the code of react-native-star-io10.podspec, as changing the podspec will not affect existing users.
Additionally, the information raised in the Issue included references to StarPrinter.ts and StarIO10Logger.ts, but we have determined that no action is necessary for these files because we created a sample of the monorepo structure and performed a simple check, which confirmed that if we make the adjustments to the podspec, we can use these files without any changes.
The timing for the implementation is likely to be several months away, so we would appreciate your patience.
If you have any other information or opinions, please feel free to reach out. Thank you for your cooperation.
👋
I've always needed to make a patch package to avoid typescript errors and installation issue (I use a mono repo) ⬇️
Would you like a PR to correct this?
My
react-native-info
:And my typescript version is 4.9.5.
The text was updated successfully, but these errors were encountered: