Closed ozonep closed 1 year ago
@ozonep Could you please add tests for this?
@kobik Something appears to be wrong, CircleCI is not returning status, wonder if we need to tweak something on CircleCI panel side. Could you please either take a look or give me admin permissions for the repo so that I could take a look? Alternatively I could add GitHub actions CI instead, that one works with zero additional setup, as opposed to Travis and CircleCI.
Will add tests now.
@kobik Something appears to be wrong, CircleCI is not returning status, wonder if we need to tweak something on CircleCI panel side. Could you please either take a look or give me admin permissions for the repo so that I could take a look? Alternatively I could add GitHub actions CI instead, that one works with zero additional setup, as opposed to Travis and CircleCI.
will check that
@ozonep seems to be ok now
@ozonep Linting is failing, could you please fix the error?
Docs updated!
@kobik This will be a semver major. Are we ready to release that already, or you'd prefer to keep current major going for a while?
@kibertoad I haven't reviewed the changes, so I can't tell by myself. can't we make it somehow backwards compatible?
@kobik We could if you strongly prefer keeping it backwards-compatible, but that would add more conditional branching, make code more heavyweight and less performant, and would expose worse API to the end user, so I would vote against it. It only affects fastify users and only those who use skiplist, though.
@kibertoad , so a major it is.
we need to add the breaking changes note in the changelog file and upgrade procedure from the previous version
@kibertoad i'd really like to this breaking change to be shipped with other breaking changes such as upgrading to ajv@8 in api-schema-build.
So we can only skip specific requests (GET/POST/etc.) for specific routes.