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 frontend and backend #6799

Closed
maciaszczykm opened this issue Feb 10, 2022 · 2 comments · Fixed by #7047
Closed

Split frontend and backend #6799

maciaszczykm opened this issue Feb 10, 2022 · 2 comments · Fixed by #7047
Assignees
@floreks @maciaszczykm
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@maciaszczykm
Copy link
Member

After moving away from Gulp scripts it should be easier right now to create a better separation between frontend and backend code like it was started in #5449. This will allow further improvements.
@maciaszczykm maciaszczykm added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 10, 2022
@maciaszczykm maciaszczykm self-assigned this Feb 10, 2022
@maciaszczykm maciaszczykm removed their assignment Mar 2, 2022
@maciaszczykm maciaszczykm pinned this issue Apr 20, 2022
@maciaszczykm
Copy link
Member Author

maciaszczykm commented Apr 20, 2022 •
edited
Loading

Proposed directory tree:

> modules
>> api
>> web

@maciaszczykm maciaszczykm mentioned this issue Apr 27, 2022
Merged
@maciaszczykm maciaszczykm added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 6, 2022
@maciaszczykm maciaszczykm added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 10, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 8, 2022
@maciaszczykm maciaszczykm added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 8, 2022
@maciaszczykm maciaszczykm unpinned this issue Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@floreks floreks

@maciaszczykm maciaszczykm

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Split frontend and backend maciaszczykm/kubernetes-dashboard
4 participants
@floreks @maciaszczykm @k8s-ci-robot @k8s-triage-robot