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(x/feegrant): Update readme #21364

Merged
merged 2 commits into from
Aug 20, 2024
Merged

docs(x/feegrant): Update readme #21364

merged 2 commits into from
Aug 20, 2024

Conversation

raynaudoe
Copy link
Contributor

@raynaudoe raynaudoe commented Aug 19, 2024

Description

this PR is part of #20955 audit process

  • Update x/feegrant/README.md to reference latest release
  • Fixed grant examples to match codebase

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
    • Updated documentation for the fee grant module to reflect the latest version.
    • Enhanced documentation with new commands and examples for querying and granting fee allowances.
    • Renamed the grants command to grants-by-grantee and introduced a new grants-by-granter command.
    • Expanded examples for the grant command to include expiration dates and allowed messages, improving clarity and usability.

Copy link
Contributor

coderabbitai bot commented Aug 19, 2024

Walkthrough

Walkthrough

The documentation for the fee grant module in the Cosmos SDK has been updated to reflect changes from version v0.47.0-rc1 to release/v0.52.x. Key improvements include updated URLs for resources, a renaming of the grants command to grants-by-grantee, and the introduction of a new command, grants-by-granter. Additionally, examples have been enriched to clarify the use of expiration dates and allowed messages, enhancing overall usability and guidance for developers.

Changes

Files Change Summary
x/feegrant/README.md Updated URLs for protocol buffer definitions and Go reference files; renamed grants to grants-by-grantee; added grants-by-granter command; enhanced grant command examples with expiration dates and allowed messages.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant FeeGrantModule
    participant GrantStorage

    User->>FeeGrantModule: Request grants-by-grantee
    FeeGrantModule->>GrantStorage: Fetch grants for grantee
    GrantStorage-->>FeeGrantModule: Return grants
    FeeGrantModule-->>User: Display grants

    User->>FeeGrantModule: Request grants-by-granter
    FeeGrantModule->>GrantStorage: Fetch grants for granter
    GrantStorage-->>FeeGrantModule: Return grants
    FeeGrantModule-->>User: Display grants
Loading

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

@raynaudoe raynaudoe added backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release and removed C:x/feegrant labels Aug 19, 2024
@raynaudoe raynaudoe marked this pull request as ready for review August 19, 2024 21:17
@raynaudoe raynaudoe requested a review from a team as a code owner August 19, 2024 21:17
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, codebase verification and nitpick comments (3)
x/feegrant/README.md (3)

338-338: Remove trailing punctuation in headings.

Headings should not have trailing punctuation.

- ###### One-time spend limit:
+ ###### One-time spend limit

- ###### Periodic spend limit:
+ ###### Periodic spend limit

- ###### With expiration:
+ ###### With expiration

- ###### With allowed messages:
+ ###### With allowed messages

Also applies to: 344-344, 350-350, 356-356

Tools
Markdownlint

338-338: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


364-369: Fix list formatting and word choice.

Use asterisks for unordered list items and replace "amount of" with "number of" for countable nouns.

- - `--spend-limit`: The maximum amount of tokens the grantee can spend
- - `--period`: The time duration in seconds for periodic allowance
- - `--period-limit`: The maximum amount of tokens the grantee can spend within each period
- - `--expiration`: The date and time when the grant expires (RFC3339 format)
- - `--allowed-messages`: Comma-separated list of allowed message type URLs
+ * `--spend-limit`: The maximum number of tokens the grantee can spend
+ * `--period`: The time duration in seconds for periodic allowance
+ * `--period-limit`: The maximum number of tokens the grantee can spend within each period
+ * `--expiration`: The date and time when the grant expires (RFC3339 format)
+ * `--allowed-messages`: Comma-separated list of allowed message type URLs
Tools
LanguageTool

[uncategorized] ~364-~364: Loose punctuation mark.
Context: ...``` Available flags: - --spend-limit: The maximum amount of tokens the grante...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~364-~364: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ... flags: - --spend-limit: The maximum amount of tokens the grantee can spend - `--pe...

(AMOUNTOF_TO_NUMBEROF)


[uncategorized] ~366-~366: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...lowance - --period-limit: The maximum amount of tokens the grantee can spend within ...

(AMOUNTOF_TO_NUMBEROF)

Markdownlint

364-364: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


365-365: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


366-366: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


367-367: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


368-368: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


258-300: Inconsistency in Command Naming in Documentation

The old command name grants is still present in several markdown files, including x/authz/README.md. This indicates that the renaming to grants-by-grantee and grants-by-granter has not been consistently applied across all relevant documentation. Please update these occurrences to maintain consistency and clarity.

  • x/authz/README.md: Multiple instances of the grants command need to be updated.
Analysis chain

Verify command renaming and consistency.

Ensure that the grants-by-grantee and grants-by-granter commands are consistently used throughout the documentation and that all examples are correctly updated.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the consistency of command renaming in the documentation.

# Test: Check for occurrences of the old and new command names. Expect: No occurrences of the old command name.
rg --type markdown 'grants\b' | rg -v 'grants-by-grantee|grants-by-granter'

Length of output: 5830

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c286e6e and 558f97f.

Files selected for processing (1)
  • x/feegrant/README.md (9 hunks)
Additional context used
Path-based instructions (1)
x/feegrant/README.md (1)

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

Gitleaks
x/feegrant/README.md

122-122: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

LanguageTool
x/feegrant/README.md

[uncategorized] ~364-~364: Loose punctuation mark.
Context: ...``` Available flags: - --spend-limit: The maximum amount of tokens the grante...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~364-~364: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ... flags: - --spend-limit: The maximum amount of tokens the grantee can spend - `--pe...

(AMOUNTOF_TO_NUMBEROF)


[uncategorized] ~366-~366: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...lowance - --period-limit: The maximum amount of tokens the grantee can spend within ...

(AMOUNTOF_TO_NUMBEROF)

Markdownlint
x/feegrant/README.md

364-364: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


365-365: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


366-366: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


367-367: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


368-368: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


338-338: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


344-344: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


350-350: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


356-356: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)

Additional comments not posted (3)
x/feegrant/README.md (3)

330-360: Verify example correctness and clarity.

Ensure that the examples for the grant command are correct and clearly demonstrate the intended functionality, including expiration dates and allowed messages.

Tools
Markdownlint

338-338: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


344-344: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


350-350: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


356-356: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


122-122: Verify and address potential API key exposure.

A generic API key has been detected in the command example. Ensure that no sensitive information is exposed in the documentation.

Tools
Gitleaks

122-122: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)


38-44: Verify URL correctness and accessibility.

Ensure that the updated URLs point to the correct and intended resources in the latest release.

Also applies to: 60-60, 74-74, 92-92, 104-116, 150-150, 168-176

Verification successful

URLs in the documentation are correct and accessible.

All updated URLs in the README.md file are accessible and correctly point to the intended resources. No further action is needed.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the accessibility of updated URLs in the documentation.

# Test: Check if URLs are accessible. Expect: HTTP status code 200 for each URL.
for url in \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/proto/cosmos/feegrant/v1beta1/feegrant.proto#L86-L96" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/fees.go#L10-L34" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/proto/cosmos/feegrant/v1beta1/feegrant.proto#L15-L33" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/proto/cosmos/feegrant/v1beta1/feegrant.proto#L35-L71" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/proto/cosmos/feegrant/v1beta1/feegrant.proto#L73-L84" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/client/cmd.go#L256-L267" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/client/tx/tx.go#L129-L131" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/auth/tx/builder.go#L208" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/proto/cosmos/tx/v1beta1/tx.proto#L216-L243" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/feegrant.pb.go#L222-L230" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/proto/cosmos/feegrant/v1beta1/tx.proto#L30-L44" \
  "https://github.com/cosmos/cosmos-sdk/blob/release/v0.52.x/x/feegrant/proto/cosmos/feegrant/v1beta1/tx.proto#L49-L62"
do
  curl -s -o /dev/null -w "%{http_code}" "$url"
done

Length of output: 17222

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

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 558f97f and f987577.

Files selected for processing (1)
  • x/feegrant/README.md (9 hunks)
Additional context used
Path-based instructions (1)
x/feegrant/README.md (1)

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

Gitleaks
x/feegrant/README.md

122-122: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

LanguageTool
x/feegrant/README.md

[uncategorized] ~364-~364: Loose punctuation mark.
Context: ...``` Available flags: - --spend-limit: The maximum amount of tokens the grante...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~364-~364: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ... flags: - --spend-limit: The maximum amount of tokens the grantee can spend - `--pe...

(AMOUNTOF_TO_NUMBEROF)


[uncategorized] ~366-~366: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...lowance - --period-limit: The maximum amount of tokens the grantee can spend within ...

(AMOUNTOF_TO_NUMBEROF)

Markdownlint
x/feegrant/README.md

364-364: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


365-365: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


366-366: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


367-367: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


368-368: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

Additional comments not posted (4)
x/feegrant/README.md (4)

258-287: Ensure consistency in command examples.

The grants-by-grantee command description and examples are clear and consistent with the rest of the documentation. No issues found.


Line range hint 289-313: Ensure consistency in command examples.

The grants-by-granter command description and examples are clear and consistent with the rest of the documentation. No issues found.


Line range hint 369-379: Ensure clarity in command descriptions.

The revoke command description and example are clear and consistent with the rest of the documentation. No issues found.

Tools
LanguageTool

[uncategorized] ~364-~364: Loose punctuation mark.
Context: ...``` Available flags: - --spend-limit: The maximum amount of tokens the grante...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~364-~364: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ... flags: - --spend-limit: The maximum amount of tokens the grantee can spend - `--pe...

(AMOUNTOF_TO_NUMBEROF)


[uncategorized] ~366-~366: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...lowance - --period-limit: The maximum amount of tokens the grantee can spend within ...

(AMOUNTOF_TO_NUMBEROF)

Markdownlint

364-364: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


365-365: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


366-366: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


367-367: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


368-368: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


Line range hint 380-411: Ensure accuracy in gRPC endpoint examples.

The gRPC endpoint descriptions and examples are clear and consistent with the rest of the documentation. No issues found.

Comment on lines +330 to +369
The `grant` command allows users to grant fee allowances to another account. The fee allowance can have an expiration date, a total spend limit, a periodic spend limit, and/or allowed messages.

```shell
simd tx feegrant grant [granter] [grantee] [flags]
```

Example (one-time spend limit):
Examples:

###### One-time spend limit

```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake
```

Example (periodic spend limit):
###### Periodic spend limit

```shell
simd tx feegrant grant cosmos1.. cosmos1.. --period 3600 --period-limit 10stake
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --period 3600 --period-limit 10stake
```

###### With expiration

```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --expiration 2024-10-31T15:04:05Z
```

###### With allowed messages

```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --expiration 2024-10-31T15:04:05Z --allowed-messages "/cosmos.gov.v1beta1.MsgSubmitProposal,/cosmos.gov.v1beta1.MsgVote"
```

Available flags:

- `--spend-limit`: The maximum amount of tokens the grantee can spend
- `--period`: The time duration in seconds for periodic allowance
- `--period-limit`: The maximum amount of tokens the grantee can spend within each period
- `--expiration`: The date and time when the grant expires (RFC3339 format)
- `--allowed-messages`: Comma-separated list of allowed message type URLs

Copy link
Contributor

Choose a reason for hiding this comment

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

Correct grammatical issues and improve list formatting.

There are grammatical issues with the use of "amount of" and list formatting inconsistencies. Here are the suggested changes:

- - `--spend-limit`: The maximum amount of tokens the grantee can spend
- - `--period`: The time duration in seconds for periodic allowance
- - `--period-limit`: The maximum amount of tokens the grantee can spend within each period
- - `--expiration`: The date and time when the grant expires (RFC3339 format)
- - `--allowed-messages`: Comma-separated list of allowed message type URLs
+ * `--spend-limit`: The maximum number of tokens the grantee can spend
+ * `--period`: The time duration in seconds for periodic allowance
+ * `--period-limit`: The maximum number of tokens the grantee can spend within each period
+ * `--expiration`: The date and time when the grant expires (RFC3339 format)
+ * `--allowed-messages`: Comma-separated list of allowed message type URLs
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The `grant` command allows users to grant fee allowances to another account. The fee allowance can have an expiration date, a total spend limit, a periodic spend limit, and/or allowed messages.
```shell
simd tx feegrant grant [granter] [grantee] [flags]
```
Example (one-time spend limit):
Examples:
###### One-time spend limit
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake
```
Example (periodic spend limit):
###### Periodic spend limit
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --period 3600 --period-limit 10stake
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --period 3600 --period-limit 10stake
```
###### With expiration
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --expiration 2024-10-31T15:04:05Z
```
###### With allowed messages
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --expiration 2024-10-31T15:04:05Z --allowed-messages "/cosmos.gov.v1beta1.MsgSubmitProposal,/cosmos.gov.v1beta1.MsgVote"
```
Available flags:
- `--spend-limit`: The maximum amount of tokens the grantee can spend
- `--period`: The time duration in seconds for periodic allowance
- `--period-limit`: The maximum amount of tokens the grantee can spend within each period
- `--expiration`: The date and time when the grant expires (RFC3339 format)
- `--allowed-messages`: Comma-separated list of allowed message type URLs
The `grant` command allows users to grant fee allowances to another account. The fee allowance can have an expiration date, a total spend limit, a periodic spend limit, and/or allowed messages.
```shell
simd tx feegrant grant [granter] [grantee] [flags]
```
Examples:
###### One-time spend limit
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake
```
###### Periodic spend limit
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --period 3600 --period-limit 10stake
```
###### With expiration
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --expiration 2024-10-31T15:04:05Z
```
###### With allowed messages
```shell
simd tx feegrant grant cosmos1.. cosmos1.. --spend-limit 100stake --expiration 2024-10-31T15:04:05Z --allowed-messages "/cosmos.gov.v1beta1.MsgSubmitProposal,/cosmos.gov.v1beta1.MsgVote"
```
Available flags:
* `--spend-limit`: The maximum number of tokens the grantee can spend
* `--period`: The time duration in seconds for periodic allowance
* `--period-limit`: The maximum number of tokens the grantee can spend within each period
* `--expiration`: The date and time when the grant expires (RFC3339 format)
* `--allowed-messages`: Comma-separated list of allowed message type URLs
Tools
LanguageTool

[uncategorized] ~364-~364: Loose punctuation mark.
Context: ...``` Available flags: - --spend-limit: The maximum amount of tokens the grante...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~364-~364: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ... flags: - --spend-limit: The maximum amount of tokens the grantee can spend - `--pe...

(AMOUNTOF_TO_NUMBEROF)


[uncategorized] ~366-~366: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...lowance - --period-limit: The maximum amount of tokens the grantee can spend within ...

(AMOUNTOF_TO_NUMBEROF)

Markdownlint

364-364: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


365-365: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


366-366: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


367-367: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


368-368: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

@julienrbrt julienrbrt added this pull request to the merge queue Aug 20, 2024
Merged via the queue into main with commit aeb0f27 Aug 20, 2024
70 checks passed
@julienrbrt julienrbrt deleted the eze/audit_feegrant_readme branch August 20, 2024 06:53
mergify bot pushed a commit that referenced this pull request Aug 20, 2024
tac0turtle pushed a commit that referenced this pull request Aug 20, 2024
Co-authored-by: Ezequiel Raynaudo <raynaudo.ee@gmail.com>
@julienrbrt julienrbrt mentioned this pull request Aug 20, 2024
28 tasks
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/feegrant
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants