-
-
Notifications
You must be signed in to change notification settings - Fork 658
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: update API tokens tag #4137
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
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.
Nice one. Minor comments.
// it tells the user what happened | ||
expect(result.description).toContain( | ||
'matches more than one option', | ||
); | ||
// it tells the user what part of the request body this pertains to | ||
expect(result.description).toContain( | ||
dataPath === '.body' | ||
? 'root object' | ||
: `${dataPath.substring('.body.'.length)} property`, | ||
); |
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.
Turns out that using multipling expect.stringContaining
on an object property doesn't work 😬
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.
Should enforce strictSchemaValidation on api-token e2e test.
Good catch @sjaanus 🥇 |
Background (general): I don’t think it creates any value. I don’t think people check the snapshot explicitly (especially now that it’s so large that it gets hidden by default), and it only creates an extra chore that you forget to do all the time (at least I do). Background (why now?): I’ve been fighting a weird issue with the snapshot test for the [API tokens OpenAPI PR](#4137). The tests run fine locally, but fail in CI. The tests seem to be using an old version of the snapshot for the test. However, when I check the snapshot in the files tab, it’s got the new and correct values. I’ve spent probably more than an hour trying to fix and debug this today but to no avail.
Background (general): I don’t think it creates any value. I don’t think people check the snapshot explicitly (especially now that it’s so large that it gets hidden by default), and it only creates an extra chore that you forget to do all the time (at least I do). Background (why now?): I’ve been fighting a weird issue with the snapshot test for the [API tokens OpenAPI PR](#4137). The tests run fine locally, but fail in CI. The tests seem to be using an old version of the snapshot for the test. However, when I check the snapshot in the files tab, it’s got the new and correct values. I’ve spent probably more than an hour trying to fix and debug this today but to no avail.
Background (general): I don’t think it creates any value. I don’t think people check the snapshot explicitly (especially now that it’s so large that it gets hidden by default), and it only creates an extra chore that you forget to do all the time (at least I do). Background (why now?): I’ve been fighting a weird issue with the snapshot test for the [API tokens OpenAPI PR](#4137). The tests run fine locally, but fail in CI. The tests seem to be using an old version of the snapshot for the test. However, when I check the snapshot in the files tab, it’s got the new and correct values. I’ve spent probably more than an hour trying to fix and debug this today but to no avail.
This PR updates endpoints and schemas for the API tokens tag.