Skip to content

Check length of unbounded string fields in messages (backport for v7)#1

Open
expertdicer wants to merge 1 commit into
release/v7.4.0-classicfrom
nguyen/v7.4.0-classic
Open

Check length of unbounded string fields in messages (backport for v7)#1
expertdicer wants to merge 1 commit into
release/v7.4.0-classicfrom
nguyen/v7.4.0-classic

Conversation

@expertdicer
Copy link
Copy Markdown

Description

Check length of unbounded string fields in messages

closes: #XXXX


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against the correct branch (see CONTRIBUTING.md).
  • Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/).
  • Added relevant godoc comments.
  • Provide a conventional commit message to follow the repository standards.
  • Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
  • Re-reviewed Files changed in the GitHub PR explorer.
  • Review SonarCloud Report in the comment section below once CI passes.

@expertdicer expertdicer changed the title Check length of unbounded string fields in messages Check length of unbounded string fields in messages (backport for v7) Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant