-
-
Notifications
You must be signed in to change notification settings - Fork 140
UserID type not used consistently #2365
Copy link
Copy link
Open
Labels
clarificationAn area where the expected behaviour is understood, but the spec could do with being more explicitAn area where the expected behaviour is understood, but the spec could do with being more explicit
Metadata
Metadata
Assignees
Labels
clarificationAn area where the expected behaviour is understood, but the spec could do with being more explicitAn area where the expected behaviour is understood, but the spec could do with being more explicit
Type
Fields
Give feedbackNo fields configured for issues without a type.
Link to problem area:
exemplary https://spec.matrix.org/v1.18/client-server-api/#molmv1curve25519-aes-sha2
Issue
Sometimes, the
typeof fields that are supposed to contain user IDs is given asstring, and sometimes asUser ID, with a link to https://spec.matrix.org/v1.18/appendices/#user-identifiers.In the example above, this is especially noticeable, as it is the case for two fields right next to each other, but the issue persists throughout the spec.
This is confusing – is the use of different types intentional, and if so, what's the reason?
Otherwise, all user ID fields should probably have type
User ID.