triniwiz / triniwiz/nativescript-plugins
Monorepo using NativeScript 7 (rather than NativeScript 8) causing type conflicts in NativeScript 8 demo apps
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 87
- Forks
- 57
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 4
Description
This is not a blocker, but does cause a lot of typings complaints in the demo app and around parts of the YogaLayout plugin.
e.g. since NativeScript 7:
- the
FontWeightenum in NativeScript Core has moved to a new file. - certain class properties in NativeScript Core have changed into ES5 accessors
I understand that there are a large number of plugins to maintain in this repo, so solving this problem might actually have detrimental consequences (i.e. migrating to NativeScript 8 may break compatibility with all of them).
Perhaps a middle ground would be for at least the YogaLayout component to specify NativeScript 8 in its package.json. Or we just keep this on the radar for the long-term.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the YogaLayout component's package.json and the NativeScript version references, then review the reported FontWeight and ES5 accessor typing conflicts in the demo app. Done means reaching an agreed NativeScript 7 or 8 compatibility approach without breaking the maintained plugins.
Written by the indexing model from the issue text.
Assessment
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100