Closed
Bug 1878834
Opened 1 year ago
Closed 1 year ago
Rename search-telemetry(-ui)-schema.json to match the collection name (include -v2) and add description and UI schema test
Categories
(Firefox :: Search, task, P3)
Firefox
Search
Tracking
()
RESOLVED
FIXED
126 Branch
| Tracking | Status | |
|---|---|---|
| firefox126 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
Details
Attachments
(1 file)
No description provided.
| Assignee | ||
Comment 1•1 year ago
|
||
In an earlier bug, we renamed the schemas in toolkit/components/search to match those of their respective collections on remote settings. We did this to make it simpler to associate the schema with the actual collection that is in use.
We should do the same with search-telemetry-schema.json and search-telemetry-schema.json, so that they become search-telemetry-v2-schema.json and search-telemetry-v2-schema.json respectively.
At the same time, we should also add a title and description to the schemas, like we've done with search-config-v2.
Severity: -- → N/A
Priority: -- → P3
Summary: Rename search-telemetry(-ui)-schema.json to match the collection name (include -v2) → Rename search-telemetry(-ui)-schema.json to match the collection name (include -v2) and add description
Updated•1 year ago
|
Assignee: nobody → scunnane
| Assignee | ||
Comment 2•1 year ago
|
||
Depends on D205250
Updated•1 year ago
|
Assignee: scunnane → standard8
Updated•1 year ago
|
Summary: Rename search-telemetry(-ui)-schema.json to match the collection name (include -v2) and add description → Rename search-telemetry(-ui)-schema.json to match the collection name (include -v2) and add description and UI schema test
Pushed by dmeehan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/302bf59a075c
Rename search-telemetry-schema to include v2 and add ui schema tests. r=scunnane
Comment 4•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox126:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 126 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•