Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Update nft docs #22060

Merged
merged 3 commits into from
Oct 3, 2024
Merged

docs: Update nft docs #22060

merged 3 commits into from
Oct 3, 2024

Conversation

lucaslopezf
Copy link
Contributor

@lucaslopezf lucaslopezf commented Oct 3, 2024

Description

ref: #21429


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Documentation
    • Added new sections for "Queries" and "Keeper Functions" in the NFT module documentation.
    • Provided detailed descriptions of available queries and functions for managing NFTs.
    • Corrected capitalization of "NFT" in the "Events" section for consistency.

Copy link
Contributor

coderabbitai bot commented Oct 3, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes in this pull request involve updates to the README.md file of the x/nft module. Two new sections, "Queries" and "Keeper Functions," have been added to provide detailed information about NFT-related queries and functions. The documentation now includes descriptions for specific queries such as Balance, Owner, and Supply, as well as functions like Mint, Burn, and Transfer. Additionally, capitalization corrections for "NFT" in the "Events" section were made to ensure consistency.

Changes

File Change Summary
x/nft/README.md Added new sections: "Queries" and "Keeper Functions" detailing NFT queries and operations. Corrected capitalization of "NFT" in the "Events" section.

Possibly related PRs

Suggested labels

C:x/authz

Suggested reviewers

  • akhilkumarpilli
  • julienrbrt
  • sontrinh16

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

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.

@lucaslopezf lucaslopezf marked this pull request as ready for review October 3, 2024 06:32
@lucaslopezf lucaslopezf requested review from alpe and a team as code owners October 3, 2024 06:32
@lucaslopezf lucaslopezf changed the title feat(nft): Update readme docs(nft): Update readme Oct 3, 2024
@lucaslopezf lucaslopezf changed the title docs(nft): Update readme docs: Update nft docs Oct 3, 2024
Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (4)
x/nft/README.md (4)

94-104: Great addition of Queries section, minor formatting suggestion.

The new Queries section provides valuable information about the available query types, enhancing the documentation's completeness. Each query is concisely described, which is helpful for users.

Consider adjusting the formatting for consistency:

-* `Balance`: Returns the number of NFTs of a given class owned by the owner.
-* `Owner`: Returns the owner of an NFT based on its class and ID.
-* `Supply`: Returns the number of NFTs from the given class.
-* `NFTs`: Queries all NFTs of a given class or owner.
-* `NFT`: Returns an NFT based on its class and ID.
-* `Class`: Returns an NFT class based on its ID.
-* `Classes`: Returns all NFT classes.
+* `Balance`: Returns the number of NFTs of a given class owned by the owner.
+* `Owner`: Returns the owner of an NFT based on its class and ID.
+* `Supply`: Returns the number of NFTs from the given class.
+* `NFTs`: Queries all NFTs of a given class or owner.
+* `NFT`: Returns an NFT based on its class and ID.
+* `Class`: Returns an NFT class based on its ID.
+* `Classes`: Returns all NFT classes.

This change removes the extra spaces before the asterisks, ensuring consistent formatting throughout the list.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...ion about NFTs and classes: * Balance: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...iven class owned by the owner. * Owner: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...FT based on its class and ID. * Supply: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~101-~101: Loose punctuation mark.
Context: ...r of NFTs from the given class. * NFTs: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~102-~102: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * NFT: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...NFT based on its class and ID. * Class: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~104-~104: Loose punctuation mark.
Context: ...n NFT class based on its ID. * Classes: Returns all NFT classes. ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)


106-119: Excellent addition of Keeper Functions section, minor formatting suggestion.

The new Keeper Functions section is a valuable addition, providing clear information about the available functions for managing NFTs. Each function is concisely described, which greatly enhances the documentation's usefulness.

Similar to the Queries section, consider adjusting the formatting for consistency:

-* `Mint`: Mints a new NFT.
-* `Burn`: Burns an existing NFT.
-* `Update`: Updates an existing NFT.
-* `Transfer`: Transfers an NFT from one owner to another.
-* `GetNFT`: Retrieves information about a specific NFT.
-* `GetNFTsOfClass`: Retrieves all NFTs of a specific class.
-* `GetNFTsOfClassByOwner`: Retrieves all NFTs of a specific class belonging to an owner.
-* `GetBalance`: Retrieves the balance of NFTs of a specific class for an owner.
-* `GetTotalSupply`: Retrieves the total supply of NFTs of a specific class.
+* `Mint`: Mints a new NFT.
+* `Burn`: Burns an existing NFT.
+* `Update`: Updates an existing NFT.
+* `Transfer`: Transfers an NFT from one owner to another.
+* `GetNFT`: Retrieves information about a specific NFT.
+* `GetNFTsOfClass`: Retrieves all NFTs of a specific class.
+* `GetNFTsOfClassByOwner`: Retrieves all NFTs of a specific class belonging to an owner.
+* `GetBalance`: Retrieves the balance of NFTs of a specific class for an owner.
+* `GetTotalSupply`: Retrieves the total supply of NFTs of a specific class.

This change removes the extra spaces before the asterisks, ensuring consistent formatting throughout the list.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...eral functions to manage NFTs: * Mint: Mints a new NFT. * Burn: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Ts: * Mint: Mints a new NFT. * Burn: Burns an existing NFT. * Update: Upda...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...Burn: Burns an existing NFT. * Update: Updates an existing NFT. * Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...: Updates an existing NFT. * Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...FT from one owner to another. * GetNFT: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...about a specific NFT. * GetNFTsOfClass: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...pecific class. * GetNFTsOfClassByOwner: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...ss belonging to an owner. * GetBalance: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~118-~118: Loose punctuation mark.
Context: ...c class for an owner. * GetTotalSupply: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)


120-147: Excellent addition of Module Architecture section.

The new Module Architecture section is a fantastic addition to the documentation. The Mermaid diagram provides a clear visual representation of the module's structure, and the accompanying explanation is thorough and helpful.

To further improve this section, consider adding a brief introduction before the diagram to set the context. For example:

## Module Architecture

The following diagram and explanation provide a high-level overview of the NFT module's architecture, illustrating how different components interact within the module and with external entities.

```mermaid
...

This addition would help readers understand the purpose of the diagram before diving into the details.

---

Line range hint `1-147`: **Overall excellent improvements to the NFT module documentation.**

The additions to this README file significantly enhance the documentation of the `x/nft` module. The new sections on Queries, Keeper Functions, and Module Architecture provide valuable insights into the module's capabilities and structure. The document now offers a more comprehensive overview, following a logical flow from abstract concepts to detailed implementation.



To further polish the document:

1. Ensure consistent formatting across all sections, particularly for bullet point lists.
2. Consider adding a table of contents at the beginning of the document to help navigate the expanded content.
3. Review the existing sections (like "State" and "Messages") to ensure they're up-to-date with any recent changes to the module.

These final touches will make the document even more user-friendly and maintainable.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary><blockquote>

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...ion about NFTs and classes:  * `Balance`: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...iven class owned by the owner. * `Owner`: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...FT based on its class and ID. * `Supply`: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~101-~101: Loose punctuation mark.
Context: ...r of NFTs from the given class. * `NFTs`: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~102-~102: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * `NFT`: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...NFT based on its class and ID. * `Class`: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~104-~104: Loose punctuation mark.
Context: ...n NFT class based on its ID. * `Classes`: Returns all NFT classes.  ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...eral functions to manage NFTs:  * `Mint`: Mints a new NFT. * `Burn`: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Ts:  * `Mint`: Mints a new NFT. * `Burn`: Burns an existing NFT. * `Update`: Upda...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...Burn`: Burns an existing NFT. * `Update`: Updates an existing NFT. * `Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...`: Updates an existing NFT. * `Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...FT from one owner to another. * `GetNFT`: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...about a specific NFT. * `GetNFTsOfClass`: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...pecific class. * `GetNFTsOfClassByOwner`: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...ss belonging to an owner. * `GetBalance`: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~118-~118: Loose punctuation mark.
Context: ...c class for an owner. * `GetTotalSupply`: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)

</blockquote></details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: .coderabbit.yml**
**Review profile: CHILL**

<details>
<summary>📥 Commits</summary>

Files that changed from the base of the PR and between 3a5a619e9d2e6e5fdfc5efaa57d42a346c0793fa and 074e08bb45f02cf0f5939d13e6a82c5de0b1eb6d.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* x/nft/README.md (2 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>📓 Path-based instructions (1)</summary><blockquote>

<details>
<summary>x/nft/README.md (1)</summary>

Pattern `**/*.md`: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"


</details>

</blockquote></details>

<details>
<summary>🪛 LanguageTool</summary><blockquote>

<details>
<summary>x/nft/README.md</summary><blockquote>

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...ion about NFTs and classes:  * `Balance`: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...iven class owned by the owner. * `Owner`: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...FT based on its class and ID. * `Supply`: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~101-~101: Loose punctuation mark.
Context: ...r of NFTs from the given class. * `NFTs`: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~102-~102: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * `NFT`: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...NFT based on its class and ID. * `Class`: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~104-~104: Loose punctuation mark.
Context: ...n NFT class based on its ID. * `Classes`: Returns all NFT classes.  ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...eral functions to manage NFTs:  * `Mint`: Mints a new NFT. * `Burn`: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Ts:  * `Mint`: Mints a new NFT. * `Burn`: Burns an existing NFT. * `Update`: Upda...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...Burn`: Burns an existing NFT. * `Update`: Updates an existing NFT. * `Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...`: Updates an existing NFT. * `Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...FT from one owner to another. * `GetNFT`: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...about a specific NFT. * `GetNFTsOfClass`: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...pecific class. * `GetNFTsOfClassByOwner`: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...ss belonging to an owner. * `GetBalance`: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~118-~118: Loose punctuation mark.
Context: ...c class for an owner. * `GetTotalSupply`: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)

</blockquote></details>

</blockquote></details>

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>x/nft/README.md (1)</summary><blockquote>

`92-93`: **LGTM: Events section update is clear and consistent.**

The update to the Events section provides a clear reference to the Protobuf definition of events. The capitalization of "NFT" has been corrected, improving consistency throughout the document.

</blockquote></details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

lgtm, but I don't think we need the module architecture section

x/nft/README.md Outdated Show resolved Hide resolved
@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Oct 3, 2024
@julienrbrt julienrbrt self-assigned this Oct 3, 2024
Copy link
Contributor

@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: 1

🧹 Outside diff range and nitpick comments (3)
x/nft/README.md (3)

25-27: Update the table of contents to match the new structure.

The table of contents should be updated to include the new "Queries" and "Keeper Functions" sections. This will improve navigation and provide a complete overview of the document's structure.

Consider adding the following lines to the table of contents:

* [Queries](#queries)
* [Keeper Functions](#keeper-functions)
🧰 Tools
🪛 Markdownlint

27-27: null
Link fragments should be valid

(MD051, link-fragments)


94-104: Improve formatting and consistency in the Queries section.

The Queries section is informative but could benefit from some formatting improvements:

  1. Consider using a colon after "The x/nft module provides several queries to retrieve information about NFTs and classes" instead of a period for better flow.
  2. Use consistent punctuation at the end of each query description (either all periods or no periods).
  3. Consider using sub-bullets or indentation to group related queries for better readability.

Here's a suggested improvement for the opening line:

The `x/nft` module provides several queries to retrieve information about NFTs and classes:
🧰 Tools
🪛 LanguageTool

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...ion about NFTs and classes: * Balance: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...iven class owned by the owner. * Owner: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...FT based on its class and ID. * Supply: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~101-~101: Loose punctuation mark.
Context: ...r of NFTs from the given class. * NFTs: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~102-~102: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * NFT: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...NFT based on its class and ID. * Class: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~104-~104: Loose punctuation mark.
Context: ...n NFT class based on its ID. * Classes: Returns all NFT classes. ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)


106-118: Enhance the Keeper Functions section for clarity and consistency.

The Keeper Functions section is well-structured, but could be improved:

  1. Use consistent punctuation at the end of each function description (either all periods or no periods).
  2. Consider grouping related functions or adding brief explanations for more complex functions.
  3. Ensure that the function names match the actual implementation in the code.

Consider verifying the exact names of these functions in the codebase to ensure accuracy in the documentation.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...eral functions to manage NFTs: * Mint: Mints a new NFT. * Burn: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Ts: * Mint: Mints a new NFT. * Burn: Burns an existing NFT. * Update: Upda...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...Burn: Burns an existing NFT. * Update: Updates an existing NFT. * Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...: Updates an existing NFT. * Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...FT from one owner to another. * GetNFT: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...about a specific NFT. * GetNFTsOfClass: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...pecific class. * GetNFTsOfClassByOwner: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...ss belonging to an owner. * GetBalance: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~118-~118: Loose punctuation mark.
Context: ...c class for an owner. * GetTotalSupply: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 074e08b and 278937f.

📒 Files selected for processing (1)
  • x/nft/README.md (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
x/nft/README.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

🪛 Markdownlint
x/nft/README.md

27-27: null
Link fragments should be valid

(MD051, link-fragments)

🪛 LanguageTool
x/nft/README.md

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...ion about NFTs and classes: * Balance: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...iven class owned by the owner. * Owner: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...FT based on its class and ID. * Supply: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~101-~101: Loose punctuation mark.
Context: ...r of NFTs from the given class. * NFTs: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~102-~102: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * NFT: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...NFT based on its class and ID. * Class: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~104-~104: Loose punctuation mark.
Context: ...n NFT class based on its ID. * Classes: Returns all NFT classes. ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...eral functions to manage NFTs: * Mint: Mints a new NFT. * Burn: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Ts: * Mint: Mints a new NFT. * Burn: Burns an existing NFT. * Update: Upda...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...Burn: Burns an existing NFT. * Update: Updates an existing NFT. * Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...: Updates an existing NFT. * Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...FT from one owner to another. * GetNFT: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...about a specific NFT. * GetNFTsOfClass: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...pecific class. * GetNFTsOfClassByOwner: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...ss belonging to an owner. * GetBalance: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~118-~118: Loose punctuation mark.
Context: ...c class for an owner. * GetTotalSupply: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)

🔇 Additional comments (1)
x/nft/README.md (1)

Line range hint 1-118: Overall improvement in documentation with room for minor enhancements.

The additions to the x/nft module documentation significantly improve its comprehensiveness and utility. The new sections on Queries and Keeper Functions provide valuable information for developers working with the module.

While the overall structure and content are good, addressing the minor formatting and consistency issues mentioned in the previous comments will further enhance the document's quality. Additionally, ensuring that the table of contents is up-to-date and all link fragments are valid will improve navigation within the document.

Great job on expanding the documentation! These updates will be very helpful for users of the x/nft module.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...ion about NFTs and classes: * Balance: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...iven class owned by the owner. * Owner: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...FT based on its class and ID. * Supply: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~101-~101: Loose punctuation mark.
Context: ...r of NFTs from the given class. * NFTs: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~102-~102: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * NFT: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...NFT based on its class and ID. * Class: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~104-~104: Loose punctuation mark.
Context: ...n NFT class based on its ID. * Classes: Returns all NFT classes. ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...eral functions to manage NFTs: * Mint: Mints a new NFT. * Burn: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Ts: * Mint: Mints a new NFT. * Burn: Burns an existing NFT. * Update: Upda...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...Burn: Burns an existing NFT. * Update: Updates an existing NFT. * Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...: Updates an existing NFT. * Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...FT from one owner to another. * GetNFT: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...about a specific NFT. * GetNFTsOfClass: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...pecific class. * GetNFTsOfClassByOwner: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...ss belonging to an owner. * GetBalance: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~118-~118: Loose punctuation mark.
Context: ...c class for an owner. * GetTotalSupply: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)

x/nft/README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (2)
x/nft/README.md (2)

91-92: Approved: Clear reference to Protobuf events

The update to the Events section is concise and informative, directing users to the authoritative source of event definitions. This change improves documentation maintainability and accuracy.

Consider adding a brief explanation of why this reference is important, e.g., "This ensures that the documentation always reflects the most up-to-date event definitions in the codebase."


93-103: Approved: Comprehensive Queries section added

The new Queries section is a valuable addition, providing clear and concise descriptions of available queries. This enhances the module's documentation significantly.

To improve readability and consistency, please adjust the formatting of bullet points:

  1. Remove the space after the asterisk for each bullet point.
  2. Ensure consistent capitalization of the first word after the query name (e.g., "Returns" vs. "Queries").

Example:

*`Balance`: Returns the number of NFTs of a given class owned by the owner.
*`Owner`: Returns the owner of an NFT based on its class and ID.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~97-~97: Loose punctuation mark.
Context: ...ion about NFTs and classes: * Balance: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...iven class owned by the owner. * Owner: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...FT based on its class and ID. * Supply: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...r of NFTs from the given class. * NFTs: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~101-~101: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * NFT: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~102-~102: Loose punctuation mark.
Context: ...NFT based on its class and ID. * Class: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...n NFT class based on its ID. * Classes: Returns all NFT classes. ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 278937f and 29144bd.

📒 Files selected for processing (1)
  • x/nft/README.md (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
x/nft/README.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

🪛 LanguageTool
x/nft/README.md

[uncategorized] ~97-~97: Loose punctuation mark.
Context: ...ion about NFTs and classes: * Balance: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...iven class owned by the owner. * Owner: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...FT based on its class and ID. * Supply: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...r of NFTs from the given class. * NFTs: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~101-~101: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * NFT: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~102-~102: Loose punctuation mark.
Context: ...NFT based on its class and ID. * Class: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...n NFT class based on its ID. * Classes: Returns all NFT classes. ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~109-~109: Loose punctuation mark.
Context: ...eral functions to manage NFTs: * Mint: Mints a new NFT. * Burn: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...Ts: * Mint: Mints a new NFT. * Burn: Burns an existing NFT. * Update: Upda...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Burn: Burns an existing NFT. * Update: Updates an existing NFT. * Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...: Updates an existing NFT. * Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...FT from one owner to another. * GetNFT: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...about a specific NFT. * GetNFTsOfClass: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...pecific class. * GetNFTsOfClassByOwner: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...ss belonging to an owner. * GetBalance: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...c class for an owner. * GetTotalSupply: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)

🔇 Additional comments (2)
x/nft/README.md (2)

Line range hint 1-117: Overall: Significant improvement to the nft module documentation

The additions to the README.md file, particularly the new Queries and Keeper Functions sections, greatly enhance the documentation of the nft module. These changes provide users with a clear overview of the module's capabilities and available functionalities.

The suggested formatting improvements and the addition of a note about referring to the source code for the most up-to-date information will further increase the document's readability and long-term maintainability.

Great work on improving the documentation! These changes will be very helpful for developers working with the nft module.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~97-~97: Loose punctuation mark.
Context: ...ion about NFTs and classes: * Balance: Returns the number of NFTs of a given c...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...iven class owned by the owner. * Owner: Returns the owner of an NFT based on it...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~99-~99: Loose punctuation mark.
Context: ...FT based on its class and ID. * Supply: Returns the number of NFTs from the giv...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...r of NFTs from the given class. * NFTs: Queries all NFTs of a given class or ow...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~101-~101: Loose punctuation mark.
Context: ... NFTs of a given class or owner. * NFT: Returns an NFT based on its class and I...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~102-~102: Loose punctuation mark.
Context: ...NFT based on its class and ID. * Class: Returns an NFT class based on its ID. *...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~103-~103: Loose punctuation mark.
Context: ...n NFT class based on its ID. * Classes: Returns all NFT classes. ## Keeper Fun...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~109-~109: Loose punctuation mark.
Context: ...eral functions to manage NFTs: * Mint: Mints a new NFT. * Burn: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...Ts: * Mint: Mints a new NFT. * Burn: Burns an existing NFT. * Update: Upda...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Burn: Burns an existing NFT. * Update: Updates an existing NFT. * Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...: Updates an existing NFT. * Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...FT from one owner to another. * GetNFT: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...about a specific NFT. * GetNFTsOfClass: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...pecific class. * GetNFTsOfClassByOwner: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...ss belonging to an owner. * GetBalance: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...c class for an owner. * GetTotalSupply: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)


105-117: Approved: Comprehensive Keeper Functions section added

The new Keeper Functions section is a valuable addition, providing clear and concise descriptions of available functions. This significantly enhances the module's documentation.

To improve readability and consistency:

  1. Remove the space after the asterisk for each bullet point.
  2. Ensure consistent sentence structure for each function description.

Example:

*`Mint`: Mints a new NFT.
*`Burn`: Burns an existing NFT.

Regarding a past review comment about generic content:

julienrbrt: This is pretty generic, let's delete this imho, as it can get out of sync quite fast

While the content is somewhat generic, it provides a useful overview of the module's capabilities. To address the concern about staying in sync:

  1. Consider adding a note at the beginning of both the Queries and Keeper Functions sections, such as:
    "Note: For the most up-to-date and detailed information, please refer to the source code and generated documentation."

  2. We can verify if this information is likely to change frequently:

This will help determine if keeping this overview is beneficial or if it's prone to becoming outdated quickly.

✅ Verification successful

Verified: Keeper Functions Documentation is Appropriate

The analysis shows that the x/nft module's keeper functions have infrequent changes over the past six months. This indicates that the Keeper Functions documentation is unlikely to become outdated quickly, making it a valuable and appropriate addition to the module's documentation.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check the frequency of changes to the nft module's queries and keeper functions
git log --since="6 months ago" --name-only --pretty=format: | sort | uniq -c | sort -rn | grep "x/nft/keeper\|x/nft/client/cli\|x/nft/client/query"

Length of output: 308

🧰 Tools
🪛 LanguageTool

[uncategorized] ~109-~109: Loose punctuation mark.
Context: ...eral functions to manage NFTs: * Mint: Mints a new NFT. * Burn: Burns an exi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~110-~110: Loose punctuation mark.
Context: ...Ts: * Mint: Mints a new NFT. * Burn: Burns an existing NFT. * Update: Upda...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~111-~111: Loose punctuation mark.
Context: ...Burn: Burns an existing NFT. * Update: Updates an existing NFT. * Transfer`: ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~112-~112: Loose punctuation mark.
Context: ...: Updates an existing NFT. * Transfer`: Transfers an NFT from one owner to anot...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~113-~113: Loose punctuation mark.
Context: ...FT from one owner to another. * GetNFT: Retrieves information about a specific ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~114-~114: Loose punctuation mark.
Context: ...about a specific NFT. * GetNFTsOfClass: Retrieves all NFTs of a specific class....

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~115-~115: Loose punctuation mark.
Context: ...pecific class. * GetNFTsOfClassByOwner: Retrieves all NFTs of a specific class ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~116-~116: Loose punctuation mark.
Context: ...ss belonging to an owner. * GetBalance: Retrieves the balance of NFTs of a spec...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~117-~117: Loose punctuation mark.
Context: ...c class for an owner. * GetTotalSupply: Retrieves the total supply of NFTs of a...

(UNLIKELY_OPENING_PUNCTUATION)

@tac0turtle tac0turtle added this pull request to the merge queue Oct 3, 2024
Merged via the queue into main with commit 9c646d8 Oct 3, 2024
68 checks passed
@tac0turtle tac0turtle deleted the lucas/nft-docs branch October 3, 2024 11:18
mergify bot pushed a commit that referenced this pull request Oct 3, 2024
(cherry picked from commit 9c646d8)
@mergify mergify bot mentioned this pull request Oct 3, 2024
12 tasks
julienrbrt pushed a commit that referenced this pull request Oct 3, 2024
Co-authored-by: Lucas Francisco López <lucaslopezf@gmail.com>
@coderabbitai coderabbitai bot mentioned this pull request Oct 23, 2024
12 tasks
@coderabbitai coderabbitai bot mentioned this pull request Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:x/nft
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants