feat: Optional filename prefix for tracks #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As @sgfn mentioned over in #194, I'm aware the recorder ecosystem is in a delicate state right now with limited bandwidth for broader changes, however, I currently have a need within my project to support a known identifier in created recordings (which I believe may be a use case others will encounter as well).
This minor change will allow for an optional prefix to be used in a track's filename (such as user id) which is useful for associating the arbitrary track ID with a known identifier (ex:
e0bc96adf4-19760930259463780812500431447.rtpx
(user_id-track_id).Thank you for considering this change!