chore: fix eslint

[jeswr]

Summary by CodeRabbit

• Bug Fixes

  • Enhanced error handling in the Writer class to manage output stream issues.
  • Ensured that the writer does not allow further writes after closure.

• Tests

  • Introduced a comprehensive suite of tests for the Writer class, validating serialization of triples and quads, and covering various edge cases and output formats.

• Chores

  • Updated the eslint dependency version in package.json.

[coderabbitai]

Walkthrough

The changes in this pull request involve two main modifications. First, the package.json file has been updated to downgrade the eslint dependency from version ^9.12.0 to ^8.57.1. Second, a comprehensive suite of tests has been added to test/N3Writer-test.js, focusing on the serialization capabilities of the Writer class. These tests cover a variety of scenarios, including edge cases, error handling, and different output formats, significantly enhancing the test coverage for the class.

Changes

File	Change Summary
package.json	Downgraded eslint from version ^9.12.0 to ^8.57.1.
test/N3Writer-test.js	Added extensive tests for the Writer class, covering serialization of triples and quads, edge cases, error handling, and output formats.

Poem

In a world of code, so bright and new,
A rabbit hops, with changes to pursue.
From eslint's heights, we take a small leap,
While tests for the writer, in bundles do sweep.
With quads and triples, we dance and we play,
Ensuring our logic won't lead us astray! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

package.json (1)

41-41: LGTM! Good choice downgrading to ESLint v8.

This is a sensible change as ESLint v9 is currently in alpha/beta. Using v8.57.1 (the latest stable version) ensures better stability and compatibility with the existing eslint plugins.

Consider adding an entry to your package.json's engines field to specify the minimum required Node.js version that's compatible with ESLint v8, although the current "node": ">=12.0" should work fine as ESLint v8 supports Node.js 12+.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3b6ff6b and f0be75b.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json (1 hunks)
• test/N3Writer-test.js (0 hunks)

💤 Files with no reviewable changes (1)

• test/N3Writer-test.js