parse-community / parse-community/parse-server
Add deprecation ID to deprecation log message
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
There is currently no logic link between a deprecation log message and the corresponding deprecation in the deprecations table.
Feature / Enhancement Description
Add the deprecation ID to the deprecator, for example:
Deprecator.logRuntimeDeprecation({
usage: 'Doing abc',
solution: 'Use xyz instead.',
id: '123',
});
Should result in a log message:
DeprecationWarning: (DEPPS123) Doing abc is deprecated and will be removed in a future version. Use xyz instead.
Example Use Case
n/a
Alternatives / Workarounds
n/a
3rd Party References
n/a
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 the Deprecator.logRuntimeDeprecation entry point and the deprecations table logic. Trace how the current deprecation message is assembled, then verify that the supplied id appears in the expected DEPPS123 format. Done means the log links the message to its deprecation ID and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100