Closed Bug 1024336 Opened 10 years ago Closed 10 years ago

[Collections App] Use canonicalName as a E.me identifier for Collections

Categories

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::Everything.me
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: amirn, Assigned: amirn)

References

Details

we are currently using categoryId which will be deprecated soon.
Assignee: nobody → amirn
Blocks: collection-app
we'll do that in 2.1
Blocks: vertical-home-next
No longer blocks: collection-app
I'm going to implement a UUID approach in bug 1022976. TBH the id does not really matter, so I think going with a normal UUID is fine. Let me know if there's any specific reason for using the canonicalName, more than happy to reopen this if there is a good reason.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
This id is for E.me server (to identify the category and return relevant results)
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Summary: [Collections App] Use canonicalName as a uuid for Collections → [Collections App] Use canonicalName as a E.me identifier for Collections
categoryId is supported by all API methods except for NativeInfo.
NativeInfo is the only one using cName.

No ETA on categoryId deprecation. If/when that changes, we can reopen.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.