feat(validation-rules-client): add maxPerPeriod operator and CadenceValue - #507
Draft
stewarthsoj wants to merge 2 commits into
Draft
stewarthsoj wants to merge 2 commits into
stewarthsoj wants to merge 2 commits into
Conversation
…denceValue Regenerated from the validation-rules-api spec that introduces cadence conditions (limit how often a context attribute may change within a period). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015pQAQfjedT9aw4USe85sY5
…eriod Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015pQAQfjedT9aw4USe85sY5
stewarthsoj
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Regenerates
@epilot/validation-rules-clientfrom the Validation Rules API spec that adds cadence conditions: a v2 rule can limit how often something may happen within a period, counting records of a bound context type (e.g. tickets linked to a contract). This is the centralised equivalent of the portal's cadence edit rules so journeys can enforce them via the validation builder.What changed
clients/validation-rules-client/src/openapi.jsonandopenapi.d.ts: newmaxPerPeriodoperator andCadenceValuecondition value (source: cadence,count: records,pathas<schema>.<date attribute>,max,period,unitwithdays | weeks | months | calendar_weeks | calendar_months), added toConditionValueonly.countis an enum so further counted kinds can be added later without touching existing rules.1.7.0-rc.0; changeset.changeset/validation-rules-cadence-operator.md(@epilot/validation-rules-clientminor,@epilot/sdkminor).The spec was generated from the API merge request rather than the deployed prod spec, because the API change (validation-rules-api !35) is not deployed yet. Publishing this rc unblocks the engine, builder and journey MRs, which already pin
1.7.0-rc.0:Test plan
npm run typegen && npm run buildin the client succeed@epilot/validation-rules-client@1.7.0-rc.0published🤖 Generated with Claude Code
https://claude.ai/code/session_015pQAQfjedT9aw4USe85sY5