Closed zehiko closed 2 weeks ago
Introduces UpdateRecordingMetadata API. For now we start simple - we can only update a single recording metadata and the caller needs to provide RecordingId i.e. we don't support update based on a filter.
UpdateRecordingMetadata
RecordingId
[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):
main
nightly
[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide
CHANGELOG.md
PR Build Summary
Recent benchmark results
Wasm size tracking
To run all checks from main, comment on the PR with @rerun-bot full-check.
@rerun-bot full-check
What
Introduces
UpdateRecordingMetadataAPI. For now we start simple - we can only update a single recording metadata and the caller needs to provideRecordingIdi.e. we don't support update based on a filter.Checklist
[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):
mainbuild: rerun.io/viewernightlybuild: rerun.io/viewer[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in
CHANGELOG.mdand the migration guidePR Build Summary
Recent benchmark results
Wasm size tracking
To run all checks from
main, comment on the PR with@rerun-bot full-check.