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.

Sign up for GitHub

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

Jump to bottom

refactor: migrate es6 -> es7 #3308

Open
5 tasks
evans-g-crsj opened this issue May 26, 2021 · 0 comments
Open
5 tasks

refactor: migrate es6 -> es7 #3308

evans-g-crsj opened this issue May 26, 2021 · 0 comments

Comments

@evans-g-crsj
Copy link
Contributor

evans-g-crsj commented May 26, 2021 •
edited
Loading

Roadmap (Epic) for arranger migration:

  • Evaluate the delta between our arranger fork and OICR arranger.
  • Create a repo that contains all that is needed to spawn an easy-to-use local env that starts arranger and ES7
  • Create a branch that contains the UI so that we can disable portions of the code that can only run with the custom arranger features. The idea is to remove as little code as possible so that the portal can run the orignal arranger along with ES7.
  • Once stabilize, add one new feature at the time. test. when all is good. create a pr to oicr with the new feature.
  • create a wrapper for the savesets that is arranger agnostic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@evans-g-crsj