We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally posted by @sckott in #189 (comment)
moving this note to a new issue.
possibly record requests made somehow so users have a record of what requests were made.
somewhat related to the work in #189 about capturing errors, but instead capture requests made
The text was updated successfully, but these errors were encountered:
Q: wonder if its better to:
i kinda lean towards the latter since then we can collect more metadata to be more useful, w/o bogging down the result objects with more data
Sorry, something went wrong.
Q: should this request provenance tracking be optional?
I think so, since it should add time to the function call. Any downsides to it being optional?
No branches or pull requests
Originally posted by @sckott in #189 (comment)
moving this note to a new issue.
possibly record requests made somehow so users have a record of what requests were made.
somewhat related to the work in #189 about capturing errors, but instead capture requests made
The text was updated successfully, but these errors were encountered: