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

Add validation for a few string fields #5487

Merged
merged 5 commits into from
Mar 5, 2024

Conversation

yiminc
Copy link
Member

@yiminc yiminc commented Mar 5, 2024

What changed?

Add string validation for a few string fields

Why?

Since we disable utf8 string validation from proto level, we want to enforce minimal validation for some key fields.

How did you test it?

Unit tests

Potential risks

No

Documentation

Is hotfix candidate?

@yiminc yiminc force-pushed the validate_utf8_string branch from fa92899 to e0e373e Compare March 5, 2024 02:18
service/frontend/workflow_handler.go Outdated Show resolved Hide resolved
service/history/command_checker.go Show resolved Hide resolved
common/searchattribute/encode_value.go Show resolved Hide resolved
service/history/command_checker.go Outdated Show resolved Hide resolved
@yiminc yiminc marked this pull request as ready for review March 5, 2024 04:38
@yiminc yiminc requested a review from a team as a code owner March 5, 2024 04:38
@yiminc yiminc merged commit dcf403f into temporalio:main Mar 5, 2024
43 checks passed
tdeebswihart pushed a commit that referenced this pull request Mar 5, 2024
## What changed?
Add string validation for a few string fields

## Why?
Since we disable utf8 string validation from proto level, we want to
enforce minimal validation for some key fields.

## How did you test it?
Unit tests

## Potential risks
No

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
stephanos pushed a commit to stephanos/temporal that referenced this pull request Mar 21, 2024
## What changed?
Add string validation for a few string fields

## Why?
Since we disable utf8 string validation from proto level, we want to
enforce minimal validation for some key fields.

## How did you test it?
Unit tests

## Potential risks
No

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
tdeebswihart pushed a commit that referenced this pull request Mar 28, 2024
Add string validation for a few string fields

Since we disable utf8 string validation from proto level, we want to
enforce minimal validation for some key fields.

Unit tests

No

<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
tdeebswihart pushed a commit that referenced this pull request Mar 28, 2024
Add string validation for a few string fields

Since we disable utf8 string validation from proto level, we want to
enforce minimal validation for some key fields.

Unit tests

No

<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
tdeebswihart pushed a commit that referenced this pull request Mar 28, 2024
Add string validation for a few string fields

Since we disable utf8 string validation from proto level, we want to
enforce minimal validation for some key fields.

Unit tests

No

<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
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.

2 participants