Consider renaming HTTP/3 "frame_type" to "type"

[LPardue]

If I understand the schema correctly, I would produce something like this

["42.797","http","frame_created",{"stream_id":"12345","frame":{"frame_type":"data"},"length":"6789"}]

since frame_type is a property of the frame object, it seems redundant. Can we just use type instead?

[rmarx]

We used to have just type or id for all similar fields, then (I think when moving to -02 or slightly before) I changed everything to have a more declarative name to make fields less reliant on context.

You could argue this is not needed for frame_type because it is indeed encapsulated in a top-level frame field, while it is still needed for stream_id because that's not immediately clear. Still, I personally somewhat prefer consistency here myself.

What would be your main argument for not keeping frame_type?

[rmarx]

Ping @LPardue

[LPardue]

I can live without this change, lets close it