chore: remove global organization id state #14135
Conversation
|
🤖 Meticulous spotted visual differences in 458 of 944 screens tested: view and approve differences detected. Last updated for commit f7879a1. This comment will update as new commits are pushed. |
| dashboard.experiments.includes("multi-organization") && | ||
| selectFeatureVisibility(dashboard.entitlements).multiple_organizations; | ||
|
|
||
| return hasMultipleOrganizations || organizationsEnabled |
There was a problem hiding this comment.
If the deployment has multiple organizations. but the organization's feature is not enabled, should this return true? The use case I'm seeing is a deployment that had access to enterprise and does not have it anymore after the trial.
There was a problem hiding this comment.
Yeah, that's the goal. We don't want swaths of the app to become unaccessible because they're in the final stages of renewing a contract with us.
|
To run this in the new workspace version after upgrading to NodeJS 20+, we have to rebase this branch with |
Closes #14057
organizationIdfrom the dashboard provider