linkedin / linkedin/linkedin.github.com
Adding of Delete features to an individual Jobs application page
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 67
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
I discovered that job application details on my Job page are still persistent on the server even after employers would have given responses to an individual. I am suggesting a new feature that will have a delete tab, so an individual can have authorization to do that, also from the developer side, one can ensure deletion can be carried out automatically since all applications are time-based.
I believe with this, it creates a win -win situation for the owner and users, saving cost due to large memory cache and also giving ones right to delete an application one might feel bad about.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the individual job application page and the server-side persistence and authorization paths; done means the requested delete control and authorized deletion behavior are defined, including the proposed time-based automatic deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100