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

Split UI from core and API #198

Open
gmazoyer opened this issue Jan 3, 2020 · 0 comments
Open

Split UI from core and API #198

gmazoyer opened this issue Jan 3, 2020 · 0 comments
Assignees
@gmazoyer
Labels
status: accepted type: enhancement Issue is considered as an enhancement to the code, so it is not a regression nor a blocking issue type: housekeeping Non-blocking task but helps to keep the code clean
Projects
Core User Interface

Comments

@gmazoyer
Copy link
Member

gmazoyer commented Jan 3, 2020

Proposed Changes

Split the code base in two to maintain the core and API on one side and the user interface on another side.

Justification

The API must be enough to write another user interface based only on REST requests and responses. It will help on keeping a focus on features and bug fixes while keeping the user interface out of the implementation logic. This should result in a more clean and stable code base for the core and API side while being able to write a modern user interface leveraging JS and async operations.
@gmazoyer gmazoyer added type: enhancement Issue is considered as an enhancement to the code, so it is not a regression nor a blocking issue type: housekeeping Non-blocking task but helps to keep the code clean labels Jan 3, 2020
@gmazoyer gmazoyer added this to the v2.0 milestone Jan 3, 2020
@gmazoyer gmazoyer self-assigned this Jan 3, 2020
@gmazoyer gmazoyer removed this from the v2.0 milestone Oct 11, 2020
@jamesditrapani jamesditrapani added this to To do in Core via automation Apr 30, 2021
@jamesditrapani jamesditrapani added this to To do in User Interface via automation Apr 30, 2021
@stale stale bot added the status: wontfix Not an issue, no fix to be done, no code to be changed label Jul 12, 2021
@peering-manager peering-manager deleted a comment from stale bot Jul 12, 2021
@stale stale bot removed the status: wontfix Not an issue, no fix to be done, no code to be changed label Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gmazoyer gmazoyer

Labels
status: accepted type: enhancement Issue is considered as an enhancement to the code, so it is not a regression nor a blocking issue type: housekeeping Non-blocking task but helps to keep the code clean
Projects
Core
To do
User Interface
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gmazoyer