Add health check to make sure emails are not used twice
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
We should add a health check to make sure emails are not used by multiple users, since that massively !@#$s up calendar scheduling.
Most user backends store that information in oc_preferences. (appid = settings, configkey = email).
We should do a simple database request and make sure emails are unique in there.
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
Search the health-check implementation and the user-backend data access around oc_preferences; start by tracing how settings with appid settings and configkey email are queried. Done means the health check identifies duplicate email values without disrupting normal scheduling checks, with coverage added wherever existing health-check tests are located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100