We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Coming from: #4
Also, can we apply Apicurio code styling if there are no objections (expecting there might be)?
Originally posted by @EricWittmann in #4 (comment)
Since the last eslint 9.x release, the configuration file formatted changed, introducing a breaking change, more information in the release post: https://eslint.org/blog/2024/04/eslint-v9.0.0-released/
The goal is to have a compatible version of the apicurio code style that works with eslint 9.x. and use it in this project
** Confirm with @EricWittmann if the latter is possible, as this could affect other consumers
The text was updated successfully, but these errors were encountered:
Pushing upstream and releasing is no problem.
Sorry, something went wrong.
@EricWittmann where is that file located?
No branches or pull requests
Context
Coming from: #4
Also, can we apply Apicurio code styling if there are no objections (expecting there might be)?
Originally posted by @EricWittmann in #4 (comment)
Goal
Since the last eslint 9.x release, the configuration file formatted changed, introducing a breaking change, more information in the release post: https://eslint.org/blog/2024/04/eslint-v9.0.0-released/
The goal is to have a compatible version of the apicurio code style that works with eslint 9.x. and use it in this project
Proposal
** Confirm with @EricWittmann if the latter is possible, as this could affect other consumers
The text was updated successfully, but these errors were encountered: