Skip to content
This repository has been archived by the owner on Jan 15, 2025. It is now read-only.

Bump SDK to 2.1.0-rc.4 #40

Merged
merged 1 commit into from
May 8, 2024
Merged

Bump SDK to 2.1.0-rc.4 #40

merged 1 commit into from
May 8, 2024

Conversation

hopr-bot
Copy link
Collaborator

@hopr-bot hopr-bot commented May 8, 2024

This Pull request contains the changeset required to be compliant with the Hoprd API version above mentioned

  • Assess that cover traffic test passes with the new SDK
  • Test Cover traffic app with the new SDK

Summary by CodeRabbit

  • New Features

    • None.
  • Bug Fixes

    • Corrected punctuation in various API documentation and test descriptions for clarity and consistency.
  • Documentation

    • Updated API documentation to reflect deprecation of the show_all_tickets endpoint.
  • Refactor

    • Updated package version from 2.1.0-rc.3 to 2.1.0-rc.4.
  • Chores

    • Updated user_agent and SDK package version in configuration files to the new version.
  • Tests

    • Updated test descriptions to match the latest API documentation changes.

@hopr-bot hopr-bot self-assigned this May 8, 2024
@hopr-bot hopr-bot requested a review from a team May 8, 2024 12:52
@hopr-bot hopr-bot enabled auto-merge (squash) May 8, 2024 12:52
Copy link

coderabbitai bot commented May 8, 2024

Walkthrough

Walkthrough

This update primarily involves minor version increments and documentation improvements across various API and test files in a Python package generated by Swagger Codegen. Key changes include the deprecation of an endpoint, the addition of punctuation for clarity in documentation, and updating the user_agent and package version to 2.1.0-rc.4.

Changes

Files Change Summary
README.md, docs/.../AliasApi.md, docs/.../ChecksApi.md, docs/.../TicketsApi.md, hoprd_sdk/api/.../alias_api.py, hoprd_sdk/api/.../checks_api.py, hoprd_sdk/api/.../tickets_api.py, test/.../test_alias_api.py, test/.../test_checks_api.py, test/.../test_tickets_api.py Documentation enhancements including punctuation corrections and clarity improvements. Deprecation of show_all_tickets endpoint.
hoprd_sdk/api_client.py, hoprd_sdk/api_client.py.orig, hoprd_sdk/configuration.py, setup.py Update of version number from 2.1.0-rc.3 to 2.1.0-rc.4. Adjustments in the user_agent value and SDK package version in configuration.

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
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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ee1cef7 and aa8c776.
Files selected for processing (14)
  • README.md (4 hunks)
  • docs/AliasApi.md (2 hunks)
  • docs/ChecksApi.md (2 hunks)
  • docs/TicketsApi.md (3 hunks)
  • hoprd_sdk/api/alias_api.py (2 hunks)
  • hoprd_sdk/api/checks_api.py (2 hunks)
  • hoprd_sdk/api/tickets_api.py (2 hunks)
  • hoprd_sdk/api_client.py (1 hunks)
  • hoprd_sdk/api_client.py.orig (1 hunks)
  • hoprd_sdk/configuration.py (1 hunks)
  • setup.py (1 hunks)
  • test/test_alias_api.py (1 hunks)
  • test/test_checks_api.py (1 hunks)
  • test/test_tickets_api.py (1 hunks)
Files skipped from review due to trivial changes (5)
  • hoprd_sdk/api/alias_api.py
  • hoprd_sdk/api/checks_api.py
  • hoprd_sdk/api/tickets_api.py
  • hoprd_sdk/api_client.py
  • setup.py
Additional Context Used
LanguageTool (31)
README.md (5)

Near line 2: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...created HOPR node and exposing it using a HTTP REST API This Python package is a...


Near line 130: It seems likely that a singular genitive (’s) apostrophe is missing.
Context: ...oldest message currently present in the nodes message inbox. MessagesApi | [**peek_...


Near line 133: It seems likely that a singular genitive (’s) apostrophe is missing.
Context: ...st of messages currently present in the nodes message inbox. MessagesApi | [**send_...


Near line 140: These punctuation marks differ from each other. Use only one if you are ending a sentence.
Context: ...ers` and `announced peers`. NodeApi | [version](docs/NodeApi....


Near line 190: This phrase is duplicated. You should probably use “API key” only once.
Context: ...thorization ## api_token - Type: API key - API key parameter name: X-Auth-Token - **Loca...

docs/AliasApi.md (14)

Near line 9: A punctuation mark might be missing here.
Context: ...s) that have this alias assigned to it. set_alias | **...


Near line 10: You might be missing the article “an” here.
Context: ...alias) | POST /api/v3/aliases | Set alias for a peer with a specific PeerId. # *...


Near line 53: Unpaired symbol: ‘[’ seems to be missing
Context: ...r, str)** ### Authorization api_token, [bearer_token]...


Near line 58: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: application/json [Back to top]...


Near line 111: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: application/json [Back to top]...


Near line 118: You might be missing the article “an” here.
Context: ... > PeerIdResponse get_alias(alias) Get alias for the PeerId (Hopr address) that have...


Near line 118: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...lias for the PeerId (Hopr address) that have this alias assigned to it. Get alias f...


Near line 120: You might be missing the article “an” here.
Context: ...at have this alias assigned to it. Get alias for the PeerId (Hopr address) that have...


Near line 120: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...lias for the PeerId (Hopr address) that have this alias assigned to it. ### Example...


Near line 165: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: application/json [Back to top]...


Near line 172: You might be missing the article “an” here.
Context: ...* > PeerIdResponse set_alias(body) Set alias for a peer with a specific PeerId. Set...


Near line 174: You might be missing the article “an” here.
Context: ...for a peer with a specific PeerId. Set alias for a peer with a specific PeerId. ###...


Near line 206: A punctuation mark might be missing here.
Context: ...----------- | ------------- body | [AliasPeerIdBodyRequest](AliasPeerIdBod...


Near line 206: A punctuation mark might be missing here.
Context: ...yRequest**](AliasPeerIdBodyRequest.md)| Alias name along with the PeerId to be aliase...

docs/ChecksApi.md (7)

Near line 11: Possible typo: you repeated a word
Context: ...Check whether the node is started. # healthyz > healthyz() Check whether the node is healthy. ...


Near line 50: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: Not defined [Back to top] [[Ba...


Near line 52: Unpaired symbol: ‘[’ seems to be missing
Context: ... Accept: Not defined [Back to top] [[Back to API list]](../README.md#do...


Near line 54: Possible typo: you repeated a word
Context: ...) [Back to README] # readyz > readyz() Check whether the node is ready to a...


Near line 93: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: Not defined [Back to top] [[Ba...


Near line 97: Possible typo: you repeated a word
Context: ...) [Back to README] # startedz > startedz() Check whether the node is started. ...


Near line 136: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: Not defined [Back to top] [[Ba...

docs/TicketsApi.md (5)

Near line 16: Specify a number, remove phrase, or simply use “many” or “numerous”
Context: ...lmost never be used as it can issue a large number of on-chain transactions. The tickets shou...


Near line 51: Unpaired symbol: ‘[’ seems to be missing
Context: ...nse body) ### Authorization api_token, [bearer_token]...


Near line 56: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: application/json [Back to top]...


Near line 106: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: application/json [Back to top]...


Near line 156: Did you mean “except”?
Context: ... - Content-Type: Not defined - Accept: application/json [Back to top]...

Ruff (6)
test/test_alias_api.py (2)

17-17: hoprd_sdk imported but unused


19-19: hoprd_sdk.rest.ApiException imported but unused

test/test_checks_api.py (2)

17-17: hoprd_sdk imported but unused


19-19: hoprd_sdk.rest.ApiException imported but unused

test/test_tickets_api.py (2)

17-17: hoprd_sdk imported but unused


19-19: hoprd_sdk.rest.ApiException imported but unused

GitHub Check Runs (1)
Lint success (9)

test/test_alias_api.py: [failure] 17-17:
[*] hoprd_sdk imported but unused


test/test_alias_api.py: [failure] 19-19:
[*] hoprd_sdk.rest.ApiException imported but unused


test/test_checks_api.py: [failure] 17-17:
[*] hoprd_sdk imported but unused


test/test_checks_api.py: [failure] 19-19:
[*] hoprd_sdk.rest.ApiException imported but unused


test/test_tickets_api.py: [failure] 17-17:
[*] hoprd_sdk imported but unused


test/test_tickets_api.py: [failure] 19-19:
[*] hoprd_sdk.rest.ApiException imported but unused

Additional comments not posted (21)
test/test_checks_api.py (1)

34-34: Update the test case description to match the updated API documentation.

Ensure that the test case reflects the new description accurately in the test implementation.

test/test_tickets_api.py (1)

41-41: Update the test case description to reflect the deprecation of the endpoint.

Ensure that the test case reflects the new description accurately in the test implementation.

test/test_alias_api.py (1)

34-34: Update the test case description to match the updated API documentation.

Ensure that the test case reflects the new description accurately in the test implementation.

docs/ChecksApi.md (4)

7-7: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.


14-14: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.


16-16: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.


30-30: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.

docs/TicketsApi.md (4)

8-8: Update the API documentation to reflect the deprecation of the endpoint.

Ensure that the documentation accurately reflects the current API behavior.


63-63: Update the API documentation to reflect the deprecation of the endpoint.

Ensure that the documentation accurately reflects the current API behavior.


65-65: Update the API documentation to reflect the deprecation of the endpoint.

Ensure that the documentation accurately reflects the current API behavior.


85-85: Update the API documentation to reflect the deprecation of the endpoint.

Ensure that the documentation accurately reflects the current API behavior.

docs/AliasApi.md (4)

7-7: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.


15-15: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.


17-17: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.


37-37: Ensure consistency in API documentation.

Verify that the method description aligns with the actual API behavior.

hoprd_sdk/configuration.py (1)

253-253: Update the SDK version in the debug report to match the new version.

Ensure that the SDK version is correctly updated across all relevant files and documentation.

README.md (4)

7-7: Update the package version to match the new SDK version.


113-113: Ensure the description for the aliases endpoint ends with a period for consistency.


125-125: Correct the description to end with a period for consistency.


145-145: Update the description to reflect the deprecation of the show_all_tickets endpoint.

hoprd_sdk/api_client.py.orig (1)

75-75: Update of user_agent to 'Swagger-Codegen/2.1.0-rc.4/python' aligns with the PR's objective to reflect the new SDK version.

@hopr-bot hopr-bot merged commit f7495a3 into master May 8, 2024
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants