Gastón Fournier 70d8f9e58a feat: add warning hints on potential misconfiguration (#2948) ... ## About the changes Add warnings when we detect something might be wrong with the customer configuration, in particular with regard to variants configuration ## Rationale Moving from variants per feature to variants per environment will allow users to have fine-grained permissions and more control over variants on different environments: #2254 But because this requires an additional step of copying variants to other environments, we identified the potential risk of users forgetting to follow this step. To keep them informed about this, we're introducing a warning sign after a toggle is enabled when we detect that: 1. The environment is enabled without variants 2. Other enabled environments have variants This situation would be a problem if you rely on `getVariant` method from the SDK, because without variants you'll receive the default variant. Probably, not what you'd expect after enabling the toggle, but there are situations where this might be correct. Because of the latter, we thought that adding a warning and letting the user handle the situation was the best solution. ## UI sketches   Co-authored-by: Nuno Góis <github@nunogois.com>		2023-01-20 18:09:01 +01:00
..
api	feat: add warning hints on potential misconfiguration (#2948)	2023-01-20 18:09:01 +01:00
helpers	feat: status API (#2931)	2023-01-19 13:27:50 +01:00
routes
seed
services	feat: add warning hints on potential misconfiguration (#2948)	2023-01-20 18:09:01 +01:00
stores
custom-auth.test.ts
health.e2e.test.ts