Is your feature request related to a problem?
I think it would be a nice convenience to allow users to populate some kind of optional schema if they so choose. Currently we do in application config validation at runtime per each read of the flagsmith value. If we could shift that validation left from runtime to config time that would be beneficial I feel.
Describe the solution you'd like.
Basically introduce another text box field to accept a json schema of some kind (ie https://json-schema.org) that gets enforced by the flagsmith UI before accepting a user's input. So going one step above markup validity and getting into domain specific validity is the idea.

Describe alternatives you've considered
Doing the current workflow of validating in app at runtime.
Additional context
No response
Is your feature request related to a problem?
I think it would be a nice convenience to allow users to populate some kind of optional schema if they so choose. Currently we do in application config validation at runtime per each read of the flagsmith value. If we could shift that validation left from runtime to config time that would be beneficial I feel.
Describe the solution you'd like.
Basically introduce another text box field to accept a json schema of some kind (ie https://json-schema.org) that gets enforced by the flagsmith UI before accepting a user's input. So going one step above markup validity and getting into domain specific validity is the idea.

Describe alternatives you've considered
Doing the current workflow of validating in app at runtime.
Additional context
No response