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

EC-002: Top Nav + Routing: Ability + Tenancy #2

Closed
angeloreale opened this issue Jan 29, 2024 · 0 comments · Fixed by #3
Closed

EC-002: Top Nav + Routing: Ability + Tenancy #2

angeloreale opened this issue Jan 29, 2024 · 0 comments · Fixed by #3
Assignees

Comments

@angeloreale
Copy link
Member

Context

This assignment introduces two business logics (image uploading and prediction) thus needing at least 2 more views.

Ask

Please add a top-nav + routing + 2 new tabs/views for the users belonging to that particular tenant (EC-001).

Solution

We already have a user pill with a sign in/out option. Since the focus is not on design, let's use the top-right side for navigation, and abstract the middle view to support the routing destinations.

Caveats

We need to be aware of the patterns we already used, and try not to be redundant (DRY)

Acceptance Criteria

User needs to be able to see at least two more tabs and navigate to them if they are logged in to the EC tenant.

  • Show org selection after login
  • Add org view switch on front end
  • Add features to Org Schema
  • Add enabled feature parser on FE build/render
  • Abstract nav panels
  • Add image uploader panel
  • Add image overlay panel

QA Steps

(optional) Write unit tests
(optional) Write integration tests

Please ask a manual QA to:

Test that a user that signed up on EC tenant sees the nav and can navigate.
Test that a user that signed up on HF tenant does not sees the nav and thus can't navigate.

Definition of Ready

This depends on EC-001

Definition of Done

PR is approved;
PR is merged to dev;

@angeloreale angeloreale converted this from a draft issue Jan 29, 2024
@angeloreale angeloreale linked a pull request Jan 29, 2024 that will close this issue
5 tasks
@angeloreale angeloreale self-assigned this Jan 29, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in NEXUS Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant