You are browsing a read-only backup copy of Wikitech. The primary site can be found at wikitech.wikimedia.org

Talk:Event Platform/Schemas/Guidelines: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Awight
(→‎Session token?: new section)
imported>Awight
Line 2: Line 2:


I would love to see some guidance about the mw.user.sessionId token.  My impression is that session_token was a common field in legacy schemas, but maybe isn't used as often in the newer events?  This help page should recommend a token (or better, a reusable fragment), or recommend against using this token. [[User:Awight|Awight]] ([[User talk:Awight|talk]]) 16:41, 27 September 2022 (UTC)
I would love to see some guidance about the mw.user.sessionId token.  My impression is that session_token was a common field in legacy schemas, but maybe isn't used as often in the newer events?  This help page should recommend a token (or better, a reusable fragment), or recommend against using this token. [[User:Awight|Awight]] ([[User talk:Awight|talk]]) 16:41, 27 September 2022 (UTC)
== Backwards compatibility ==
I seem to run into this requirement often and still don't fully understand what's safe.  Do changes need to be both backwards- ''and'' forwards-compatible, meaning that an old event is valid according to the new schema, and a new event is valid according to the old schema?  This would make even the migration listed on the wiki (adding an optional field) impossible, so I think we're only talking about strict backwards-compatibility.  In this case, there are other possible changes such as * adding enum values, * providing min/max on an integer, making an optional field into a required field... [[User:Awight|Awight]] ([[User talk:Awight|talk]]) 10:32, 29 September 2022 (UTC)

Revision as of 10:32, 29 September 2022

Session token?

I would love to see some guidance about the mw.user.sessionId token. My impression is that session_token was a common field in legacy schemas, but maybe isn't used as often in the newer events? This help page should recommend a token (or better, a reusable fragment), or recommend against using this token. Awight (talk) 16:41, 27 September 2022 (UTC)

Backwards compatibility

I seem to run into this requirement often and still don't fully understand what's safe. Do changes need to be both backwards- and forwards-compatible, meaning that an old event is valid according to the new schema, and a new event is valid according to the old schema? This would make even the migration listed on the wiki (adding an optional field) impossible, so I think we're only talking about strict backwards-compatibility. In this case, there are other possible changes such as * adding enum values, * providing min/max on an integer, making an optional field into a required field... Awight (talk) 10:32, 29 September 2022 (UTC)