Fix Linting Errors - #13699
Conversation
|
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7cd1a67062
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| console.log( errs ); | ||
| <!-- lint disable first-heading-level expected-html-sections --> | ||
| <!-- Section to include announcements. If section is included, add a horizontal rule *after* the section. Make sure to keep an empty line after the `section` element and another before the `/section` close. --> | ||
| <section class="announcement"> |
There was a problem hiding this comment.
Restore a runnable JavaScript example
This file is still a .js example under the package's ./examples directory, but the replacement content is HTML/Markdown markup. When the example is executed or even syntax-checked with Node, it fails with SyntaxError: Unexpected token '<' at the <section> tag, so the schema validation example no longer runs and example checks for this package will fail.
Useful? React with 👍 / 👎.
What was broken
A linter error in our JavaScript code is preventing the project from passing automated checks.
What changed
We are fixing the error by updating our usage of template literals to be more consistent with best practices.
How to test
Run the automated tests and check that the linter errors have been resolved.