-
Notifications
You must be signed in to change notification settings - Fork 148
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
feat: lint arazzo test descriptions #1601
Conversation
🦋 Changeset detectedLatest commit: 54bce55 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success750 tests passing in 105 suites. Report generated by 🧪jest coverage report action from 54bce55 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments. Otherwise looks good.
984b545
to
2fde553
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a small thing, but we should also update the CLI help output to add arazzo to the lint command description.
Linting some of the Arazzo examples from the main project, I get some errors "The field in
must be present on this level." but the entry looks like this:
workflowId: place-order
parameters:
- name: pet_id
value: $steps.find-pet.outputs.my_pet_id
Looking at the spec document for parameters, I think the "in" isn't required when it's a reference to something that's already in the scope of an Arazzo workflow.
c9e47b8
to
3ffe7bb
Compare
Thanks Lorna, |
We don't have support for references in step parameters (or I'm doing something wrong! Testing the pet coupons example ), will we list that as not supported, or should we add it? https://github.com/OAI/Arazzo-Specification/blob/main/versions/1.0.0.md#step-object |
69b85df
to
ead188a
Compare
ead188a
to
9e020fb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there. A few more comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice, works well with the samples in the main project (and I have some tiny fixes to send them that I found using this tool, so it's already proven its value!. Nice work!
* feat: lint arazzo test descriptions
What/Why/How?
Add Arazzo validation to the
lint
cli command.Now it is possible to lint Arazzo description file by running
redocly lint museum.yaml
Reference
Testing
Screenshots (optional)
Check yourself
Security