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

Migrating the Application Main Frame #1000

Open
bruderol opened this issue Feb 5, 2020 · 1 comment
Open

Migrating the Application Main Frame #1000

bruderol opened this issue Feb 5, 2020 · 1 comment
Assignees
Labels
complexity:4-Epic Complexity "Epic" --> to be split further into sub stories contributorWanted For special tasks that are well defined and could need a contributor who is willing to do it. topic:client-modernisation

Comments

@bruderol
Copy link
Member

bruderol commented Feb 5, 2020

Get the frontend mainframe of scenarioo (branch & build selection, comparison selection, breadcrumbs, tabs etc.) migrated from AngularJS to Angular.

This is an epic - needs some planning and break up into smaller stories

Acceptance criteria

  • new nice services or other mechanism is defined on how the pages communicate with the frame about stuff like
    • getting branch and build selection
    • getting comparison selection
    • providing information to display in breadcrumbs (which use case is selected, which scenario, which page, which step or which object and so on ... NOT like now: parsing it from URL in a human readable way, which is the wrong way to go!)
  • new pages should not depend on any old angular services anymore but only on new nicely designed services with more nicer and more convenient way to attach to this information
  • for old pages an adapter replacement for the old services might be needed such that old (still unmigrated pages) work until they are migrated

Implementation Details

  • Needs some new services to be defined that can be used nicely in the new pages (e.g. for getting branch, build and comparison selection or to provide some context information etc.) and some adpaters might be needed to make the old pages still work with the old services inside the new frame.
@bruderol bruderol added complexity:3-Hard Complexity hard but still doable in a sprint (2-3 weeks) contributorWanted For special tasks that are well defined and could need a contributor who is willing to do it. complexity:4-Epic Complexity "Epic" --> to be split further into sub stories and removed complexity:3-Hard Complexity hard but still doable in a sprint (2-3 weeks) labels Feb 5, 2020
@bruderol
Copy link
Member Author

bruderol commented Feb 5, 2020

1000 💯 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity:4-Epic Complexity "Epic" --> to be split further into sub stories contributorWanted For special tasks that are well defined and could need a contributor who is willing to do it. topic:client-modernisation
Projects
Development

No branches or pull requests

2 participants