ui: Migrate from Marionette to React
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- react
- Domain
- frontend
Research direction
The issue names no files, tests or entry points, so start by finding the existing Marionette views and the earlier React explorations in the repository. Read the two linked migration articles on a hybrid adapter layer that runs Marionette and React side by side. Done would mean an agreed migration plan with the first screen moved behind that adapter, which the maintainers have not yet decided on.
Written by the indexing model from the issue text.
Description
About
The repository already includes a few explorations to bring in React and MUI, but those have been ramblings from many years ago, without digesting too much knowledge about relevant internals.
Idea
Grafana migrated from Angular to React the other day, providing a hybrid adapter layer for the transitioning period that supported both frameworks.
Next
The nice articles Gentle Migration from Marionette to React by @jgaskins and Transitioning Your Marionette App to React by @msholty-fd just found us; both elaborate about such an adapter layer to run both Marionette and React in parallel, suitable for optimal progressive transitioning. Thank you very much!
- Dominant language
- Python
- Stars
- 123
- Forks
- 31
- Avg merge
- 3h 7m
- Merged PRs (30d)
- 71
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from ip-tools/patzilla
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ip-tools/patzilla#139 · 3 comments ·
Maintainers usually reply within 1 day
-
UI: Update BabelOpendependencies help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 20/100
ip-tools/patzilla#188 · 1 comment ·
Maintainers usually reply within 1 day
-
dependencies help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
ip-tools/patzilla#181 · 1 comment ·
Maintainers usually reply within 1 day
All issues in ip-tools/patzilla
Similar issues
-
bug module:nodes tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rocketride-org/rocketride-server#3020 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
bretterer/home-assistant-rivian#335 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mampfes/hacs_waste_collection_schedule#8114 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TIGER-AI-Lab/ClawBench#475 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
UKGovernmentBEIS/inspect_ai#6322 ·
Maintainers usually reply within 1 day