Repository navigation
API: Remove redundant keys and add inline support for validators #1340
Description
Is your feature request related to a problem?
The current API has redundant keys like type and tag that serve no purpose beyond logging, which clutters the interface. Additionally, there is no support for inline validators, limiting flexibility.
Describe the solution you'd like
- Remove type and tag keys from the API.
- Add support for inline validators.
Original issue
Describe the current behavior
Couple of redundant keys i.e type/tag are nominal and do not serve any purpose other than logging. Hence its prudent to drop them. Additionally, added support for inline validators along with the validator config support that we currently have.
Describe the enhancement you'd like
Drop type, tag keys and add support for inline validators
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[-]Guadrails: Add support for inline validators in standalone guardrails and remove unused keys from API endpoint[/-][+]API: Remove redundant keys and add validators[/+][-]API: Remove redundant keys and add validators[/-][+]API: Remove redundant keys and add inline support for validators[/+]github-actions commentedon Nov 10, 2026
🎉 This issue has been resolved in version 1.9.0-main.8 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀