Removed use of deprecated ioutil

[sacOO7]

• As per official doc, ioutil module is replaced by io or os since go 1.16
• Link -> https://pkg.go.dev/io/ioutil

Summary by CodeRabbit

• Bug Fixes

  • Replaced deprecated ioutil package functions with io package functions to enhance code stability and clarity across multiple components.

• Refactor

  • Streamlined code by removing dependencies on the deprecated ioutil package, improving adherence to current best practices in Go programming.

These changes ensure better maintainability and performance of the application.

[coderabbitai]

Walkthrough

The changes across various files involve replacing deprecated ioutil package functions with their io package equivalents. This includes updates to reading HTTP response bodies and handling request bodies, ensuring the code adheres to the latest Go programming standards. The modifications do not alter the logic or functionality of the affected components.

Changes

Files	Change Summary
ably/auth.go, ably/error.go, ably/rest_client.go, ablytest/sandbox.go	Replaced ioutil.ReadAll with io.ReadAll to comply with the deprecation of the ioutil package.
ably/rest_client_integration_test.go	Updated TestRestClient to use io.ReadAll instead of ioutil.ReadAll.
ablytest/proxies.go	Removed ioutil import and replaced ioutil.ReadAll with io.ReadAll in the Query function.
ablytest/recorders.go	Replaced ioutil.NopCloser with io.NopCloser, modifying the body function implementation.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    Client->>Server: Send HTTP Request
    Server->>Server: Read Request Body using io.ReadAll
    Server-->>Client: Send HTTP Response
    Client->>Server: Process Response using io.ReadAll

Loading

🐇 "In the code where changes bloom,
No more ioutil, we make room.
With io now taking the lead,
Our functions grow, they take the heed.
A hop towards the latest way,
In Go, we code, and play all day!" 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f749c38 and f8a27da.

Files selected for processing (7)

• ably/auth.go (3 hunks)
• ably/error.go (2 hunks)
• ably/rest_client.go (3 hunks)
• ably/rest_client_integration_test.go (3 hunks)
• ablytest/proxies.go (2 hunks)
• ablytest/recorders.go (3 hunks)
• ablytest/sandbox.go (2 hunks)

Files skipped from review due to trivial changes (6)

• ably/auth.go
• ably/error.go
• ably/rest_client.go
• ably/rest_client_integration_test.go
• ablytest/proxies.go
• ablytest/sandbox.go

Additional comments not posted (1)

ablytest/recorders.go (1)

248-249: Change to io.NopCloser is appropriate.

The update from ioutil.NopCloser to io.NopCloser is correct and aligns with the deprecation of the ioutil package. The functionality remains consistent.

[ttypic]

LGTM