-
Notifications
You must be signed in to change notification settings - Fork 66
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
Remove trickle down router props #4076
Conversation
…Membership and isVisitingAdmin
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4076 +/- ##
=======================================
Coverage 78.72% 78.72%
=======================================
Files 284 284
Lines 13009 13009
Branches 2897 2897
=======================================
Hits 10241 10241
Misses 2768 2768
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
I won't be able to review this today, so if someone else can step in, would appreciate it. My main point of concern is that if a user is logged in and viewing Team 1, and they directly navigate in the browser to a Team 2 page (e.g. viewing instances) that the new view reflects the correct team's data |
I added two new tests to cover these specific scenarios |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're missing an opportunity for the permissionsMixin
in pages/application/Overview.vue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joepavitt I went through this line by line with Serban . We found 1 left over prop and fixed that.
did a full review on pre-staging, tested all pages touched (with dev tools console open) and direct url access to alt teams etc.
I am happy to approve but will not merge as you may see something i dont
@Steve-Mcl thanks Steve, just left my own comments on this too |
…' into remove-trickle-down-router-props
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all good from my pov.
Remove trickle down router props and cohesive way of using team, teamMembership and isVisitingAdmin
Description
Focusing mainly on teamMembership & team props which can be used directly from the permissionsMixin, or using accessing the account store directly where the permission mixin is not used.
The isVisitingAdmin computed prop has also been moved in the permissionsMixin
Related Issue(s)
none
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
area:migration
label