You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@mudler why is it possible to define the users in the different stages?
With the current way, I build the schema validation, it will be possible to check every place where the users can be defined, but, it might make the schema very hard to read. So, if we have to support such scenarios in multiple stages, I'm thinking I'll have to add a second tier of validations, so I can keep the schema a bit more simple. However, my main desire to keep everything on a JSON schema, is that any other tool can read it and ensure validation on their own, i.e., there's no hidden magic or need to dig into the code. WDYT?
Ok, Itxaka explained this a bit more in detail, so it's clear I have to support it. I will think about those two options and come back with more info to share with the team and get some feedback
The validator is currently warning about this config
With the message
This is because the current schema expects users to be defined at the root level.
The text was updated successfully, but these errors were encountered: