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.

Sign up for GitHub

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

Jump to bottom

Implement negative tests for (set_once) and (goes) #175

Open
yevhenii-nadtochii opened this issue Dec 27, 2024 · 0 comments
Open

Implement negative tests for (set_once) and (goes) #175

yevhenii-nadtochii opened this issue Dec 27, 2024 · 0 comments

Comments

@yevhenii-nadtochii
Copy link
Contributor

Currently, the suites for the mentioned options do not cover negative scenarios, in which the compilation should fail.

Please implement the following tests:

  1. Fail when the option is applied to unsupported field types.
  2. Additionally, make sure the (set_once) works well when it is applied to an external type (which comes from dependencies) like Google's Timestamp. We had a bug related to this, so better to have this positive test as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yevhenii-nadtochii