-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
openapi-v3-types module: add basic tests #181
Comments
I'm not sure if this issue is valid anymore. We've dropped v3 to v2 conversion from MVP (as far as I know) and we have validation for v3 in I think we should repurpose this issue to add in what we discussed here #754 (comment) and then re-estimate it. @strongloop/lb-next-dev thoughts? |
@shimks I don't think this is done in #753, we don't have tests for package
Could you summarize a little bit what are we adding in this issue? tests for |
I think the fact that we need to ask this question is an indication that this story needs re-grooming. |
I guess we need clarification from @bajtos who created this issue? |
Looking at this issue again, I'm thinking maybe the acceptance criteria is clear enough? The title of this ticket is Should we leave adding tests for |
Now that I've taken a look at this issue again, I think it's fine as it is now :p (sorry for the confusion). I personally think adding in tests for |
ok. i'll remove |
|
Add basic tests to verify that example OpenAPI v3 documents and Swagger documents (via converter) can be compiled against the type definition. Create test infrastructure that makes it easy to add focused tests in the future.
This is a follow-up issue for #177.
Acceptance Criteria
BLOCKED BY
The text was updated successfully, but these errors were encountered: