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

Support out-of-tree platforms #2211

Open
1 of 5 tasks
tido64 opened this issue Sep 9, 2024 · 2 comments
Open
1 of 5 tasks

Support out-of-tree platforms #2211

tido64 opened this issue Sep 9, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@tido64
Copy link
Member

tido64 commented Sep 9, 2024

Motivation

It's currently hard to add new platforms to RNTA without contributing directly in the repository.

Solution

Move platform folders to separate packages and design a plugin interface so that platforms can be sourced from third-party packages.

Work

  • Breaking changes in 4.0 #1797
    • This work is mostly to reduce the surface area and avoid conflicts
  • Convert the repository to a monorepo
    • We will have to migrate away from semantic-release since it does not support monorepos
  • Move template configuration to their respective platform folders
  • Move platform folders to separate packages
  • Design plugin interface for out-of-tree platform packages
@tido64 tido64 added the enhancement New feature or request label Sep 9, 2024
@mikehardy
Copy link

If those items were numbered, then

3- move template config to platform folder, and
5- design plugin interface

...seem like things that could happen in parallel and be backwards compatible with current state? (could be wrong on item 3 and backwards compatible, I am unsure)

My point in mentioning that is that repo reorg vs items 3 and 5 might be pursued separately and if they were, then out-of-tree experimentation could be unblocked and possible immediately by pursuing them with a narrow focus...

@tido64
Copy link
Member Author

tido64 commented Nov 4, 2024

My point in mentioning that is that repo reorg vs items 3 and 5 might be pursued separately and if they were, then out-of-tree experimentation could be unblocked and possible immediately by pursuing them with a narrow focus...

I think that's probably right. They can be pursued separately. But doing them in order is probably less churn? At the very least, it should be clearer where the lines are, which in turn should make it easier to find commonalities between the platforms we have today once platform specifics are compartmentalized and extracted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants