-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Approvals Api does not work with replacing rules #11
Comments
Thanks again @chrisdurand-RL - I'm following up with my team and will get back to you with a timeline for a fix. |
Hi there, Any update here? Our launch is currently blocked on this issue. Who can we reach out to can an update? |
Hi @tonyurso-RL, we are actively investigating the issues and working towards a new release with all the identified fixes. I'll update when we have a clear timeline to provide. |
Can you recommend any workarounds at the moment?
…On Thu, May 12, 2022, 5:51 PM carmenquan ***@***.***> wrote:
Hi @tonyurso-RL <https://github.com/tonyurso-RL>, we are actively
investigating the issues and working towards a new release with all the
identified fixes. I'll update when we have a clear timeline to provide.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQKF3LPTXIXBWSALGMXYQXTVJWRR7ANCNFSM5VWUDMKA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @tonyurso-RL, The correct way to populate instructions for this request is using the raw dictionary, not using the model for |
Hello, do you have any updates for this bug? |
Hey Chris, just sent you an email with an update. |
When doing a rule replacement, the semantic patch expects the field
variationId
to be present. However, the internal model for Rule has a propertyvariation
. These are incompatible and the service throws an error.As you can see from the model for Rule, the attribute is called
variation
, notvariationId
.I can try to use a raw dictionary that conforms to the semantic patch pattern, but then I get a different error:
The text was updated successfully, but these errors were encountered: