Bump SDK to v2.0

[Strift]

This is a draft PR to see CI results.

Related issue

See #749 for discussion regarding v2.0

Summary by CodeRabbit

• Refactor

  • Replaced custom JSON encoding/decoding exceptions with the standard PHP \JsonException throughout the application.
  • Updated error messages related to JSON errors for clarity and consistency.

• Tests

  • Adjusted tests to expect \JsonException and updated related error message assertions.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This change removes custom JSON exception classes and replaces their usage throughout the codebase with PHP's built-in \JsonException. All relevant docblocks, exception handling, and test expectations are updated accordingly. The custom exception classes are deleted, and their references are removed from imports and documentation.

Changes

Files/Groups	Change Summary
src/Contracts/Http.php, src/Http/Serialize/SerializerInterface.php, src/Http/Client.php	Updated docblocks to use @throws \JsonException instead of custom exceptions; removed related imports.
src/Exceptions/JsonEncodingException.php, src/Exceptions/JsonDecodingException.php	Deleted custom exception classes.
src/Http/Serialize/Json.php	Removed try-catch blocks and custom exception wrapping; now directly throws \JsonException.
tests/Endpoints/DocumentsTest.php, tests/Http/ClientTest.php, tests/Http/Serialize/JsonTest.php	Updated tests to expect \JsonException and adjusted expected exception messages; removed custom exception imports.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Serializer (Json)
    participant PHP Engine

    Client->>Serializer (Json): serialize(data)
    Serializer (Json)->>PHP Engine: json_encode(data, JSON_THROW_ON_ERROR)
    alt On error
        PHP Engine-->>Client: throws \JsonException
    else Success
        PHP Engine-->>Serializer (Json): JSON string
        Serializer (Json)-->>Client: JSON string
    end

Loading

Possibly related PRs

• meilisearch/meilisearch-php#759: The main PR and the retrieved PR both make identical changes to replace custom JSON exceptions with PHP's built-in \JsonException across the same files and methods, including updates to interface docblocks, exception class removals, and test adjustments.

Suggested labels

breaking-change

Suggested reviewers

• brunoocasali
• norkunas

Poem

A hop, a leap, a JSON cheer,
Custom exceptions disappear!
Now with PHP’s own in tow,
Errors are clearer—let them show!
Tests and docs all join the fun,
Simpler code for everyone.
🐇✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch v2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[norkunas]

I don't understand this. Shouldn't there be a v1 branch and the main would be v2? Now I see v2 branch, and main as v1