infinitered / infinitered/authority_ecto
Store locking information on User Schema
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 12
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Devise tracks this information using two columns:
- failed_attempts (integer)
- locked_at (datetime)
I'm curious why the attempts and locks tables are necessary, especially because it results in performing an extra query on every single request.
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
Start by reading the User Schema and the attempts and locks tables, then trace the extra query performed on each request. Determine whether failed_attempts and locked_at can replace the existing tables without changing locking behavior; the issue does not name files or tests, so the relevant entry points and completion checks must first be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- authentication, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100