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

request {resource}_id even if the resource is not declarative-friendly. #1107

Closed
toumorokoshi opened this issue Mar 2, 2023 · 3 comments · Fixed by #1155
Closed

request {resource}_id even if the resource is not declarative-friendly. #1107

toumorokoshi opened this issue Mar 2, 2023 · 3 comments · Fixed by #1155
Labels
priority: p3 type: feature request
Milestone
gcp-strict-aips

Comments

@toumorokoshi
Copy link
Contributor

Generally, having user-settable IDs is a better user experience, and it would be best to require them and exempt yourself in edge cases rather than not enforce it.

See aip-dev/google.aip.dev#1019 which also recommends upgrading the guidance.
@toumorokoshi toumorokoshi added this to the gcp-strict-aips milestone Mar 2, 2023
@toumorokoshi toumorokoshi mentioned this issue May 19, 2023
Merged
@SsomsakTH
Copy link

Generally, having user-settable IDs is a better user experience, and it would be best to require them and exempt yourself in edge cases rather than not enforce it.

See aip-dev/google.aip.dev#1019 which also recommends upgrading the guidance.

2 similar comments
@SsomsakTH
Copy link

Generally, having user-settable IDs is a better user experience, and it would be best to require them and exempt yourself in edge cases rather than not enforce it.

See aip-dev/google.aip.dev#1019 which also recommends upgrading the guidance.

@SsomsakTH
Copy link

Generally, having user-settable IDs is a better user experience, and it would be best to require them and exempt yourself in edge cases rather than not enforce it.

See aip-dev/google.aip.dev#1019 which also recommends upgrading the guidance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: p3 type: feature request
Projects
None yet
Milestone
gcp-strict-aips
Development

Successfully merging a pull request may close this issue.

feat(AIP-133): add request-id-field for non-df API
2 participants
@toumorokoshi @SsomsakTH