Skip to content

Add data tracks schema metadata#1516

Draft
ladvoc wants to merge 2 commits intomainfrom
ladvoc/data-track-schema
Draft

Add data tracks schema metadata#1516
ladvoc wants to merge 2 commits intomainfrom
ladvoc/data-track-schema

Conversation

@ladvoc
Copy link
Copy Markdown
Contributor

@ladvoc ladvoc commented Apr 24, 2026

Resolves BOT-318

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 24, 2026

⚠️ No Changeset found

Latest commit: 64f12c0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR
Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

Encryption.Type encryption = 3;

// Schema describing frames published on the track.
optional DataTrackSchema schema = 4;
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this the mechanism which clients will get the schema of a DataTrack?

Comment thread livekit/livekit_rtc.pb.go
(*ClientInfo)(nil), // 89: livekit.ClientInfo
(ReconnectReason)(0), // 90: livekit.ReconnectReason
(*DataTrackSubscriptionOptions)(nil), // 91: livekit.DataTrackSubscriptionOptions
(*DataTrackSchema)(nil), // 75: livekit.DataTrackSchema
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For my understanding, is this a breaking change?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, all protocol additions are purely additive and older clients will ignore fields they do not recognize (one of the advantages to Protobuf).

@chenosaurus chenosaurus marked this pull request as ready for review April 25, 2026 00:29
@chenosaurus chenosaurus marked this pull request as draft April 25, 2026 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants