Skip to content

normalize protobuf "id" log field names#1451

Merged
paulwe merged 3 commits intomainfrom
normalize-json
Mar 15, 2026
Merged

normalize protobuf "id" log field names#1451
paulwe merged 3 commits intomainfrom
normalize-json

Conversation

@paulwe
Copy link
Copy Markdown
Contributor

@paulwe paulwe commented Mar 15, 2026

No description provided.

@paulwe paulwe requested a review from a team March 15, 2026 10:50
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Mar 15, 2026

🦋 Changeset detected

Latest commit: 387aa64

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another 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.

paulwe and others added 2 commits March 15, 2026 03:51
Updated the changeset to include a patch for '@livekit/protocol' and normalize protobuf 'id' log field names.
@paulwe paulwe requested a review from a team March 15, 2026 10:55
string room_name = 6;
string participant_id = 7;
string track_id = 8;
string participant_id = 7 [(logger.name) = "participantID"];
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would have been nice to call this pID as that is what is used everywhere, but will look odd here.

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.

we could do this but this is going to go into customer facing logs. maybe we should abandon the old convention in the interest of clarity? it's easy to change if you'd prefer pID

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No, I think clarity is more important. I think we should move other logs to this, but that could take a while

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.

nah, i did this in about 5 minutes with claude... i think we can change it everywhere without much more effort. i'll submit a pr after i land this

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Oh cool. Thank you.

@paulwe paulwe merged commit 48d85c2 into main Mar 15, 2026
11 checks passed
@paulwe paulwe deleted the normalize-json branch March 15, 2026 11:07
This was referenced Mar 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants