Currently:
- performer.session_id
- performer.active_browsing_session_token
- performer.pageview_id
all have the same restrictions:
maxLength: 20 minLength: 20 pattern: '^[0-9a-z]{20}$'
Making it impossible to use the schemas for instrumentation outside of wikis where the Test Kitchen SDKs are not available.
For example, it would be great to record a session ID generated by randomUUID() but that generates a 36-character v4 UUID (e.g. "36b8f84d-df4e-4d49-b662-bcde71a8764f") which is incompatible with the current validation rule.
Furthermore, eventually we want to move current session ID generation in the SDKs to UUID (T266813), so this would help with that.
This change would require a major version bump for the schema. Therefore, first do some light research on what other changes we want to make that require major version bumps and group them together. (timebox this)
Acceptance criteria
- All "major-version-bumping" tasks found above have been added as a subtask of this
- web/base and app/base schemas updated with looser validation rules for those identifiers (just max character length of 64)
- extension schemas (e.g. web/translation) also updated