You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the reasons described here and here we should use the WithoutTimeout variants of resource (and data source) CRUD handlers over the Context variants.
Implement semgrep rules to catch setting of CreateContext, ReadContext, UpdateContext or DeleteContextschema.Resource fields
Ensure documentation uses the WithoutTimeout variants
Convert all existing references
The text was updated successfully, but these errors were encountered:
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
ewbankkit
changed the title
Prefer WithoutTimeout variants over Context variants of resource CRUD handlers
Prefer WithoutTimeout variants over Context variants of resource CRUD handlers
Dec 16, 2022
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
For the reasons described here and here we should use the
WithoutTimeout
variants of resource (and data source) CRUD handlers over theContext
variants.semgrep
rules to catch setting ofCreateContext
,ReadContext
,UpdateContext
orDeleteContext
schema.Resource
fieldsWithoutTimeout
variantsThe text was updated successfully, but these errors were encountered: