parse-community / parse-community/parse-server
Make objectId lexographically sortable
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
objectID is not sortable by creation time.
Feature / Enhancement Description
Implement ULID spec based on https://www.npmjs.com/package/ulid-workers
One also don't need to store createdAt separately anymore and objectId can be sorted based on creation time without conflicts that might arise when you clone multiple objects from dashboard.
Example Use Case
I wanted to implement cursor based pagination. I wanted to say less than objectID with x limit to load next batch of items.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how Parse Server generates and stores objectID and createdAt values, then compare the required behavior with the ULID specification and the ulid-workers package linked in the issue. Check how cursor-based pagination would use lexicographic IDs; done means IDs sort by creation time, remain conflict-free when objects are cloned, and support the stated pagination use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100