BUG: Making SignUp/SignIn easier for new contributors/users.
Nobody has claimed this yet.
- #214 by @PranjaliBhardwaj — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- authentication
Research direction
Start by tracing the SignUp and SignIn entry points and checking how existing-user and email-verification outcomes are currently reported. Done means users receive clear messages for recognized accounts and verification-link delivery, with the relevant authentication flow behaving consistently.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
🎯 Expected Behavior
Whenever you SignUp/SignIn, you should see some messages like "this is an registered email account" or "we have sent you verification link, check your email".
🚨 Actual Behavior
On Signup/Signin, project isnt showing if its old user or new user. or if there is a verification link I should see in my email. When you login/signup you may face some confusion due to lack of given information. I am sure I am not only one who faced this issue when exploring and understanding project.
Record
- I agree to follow this project's Code of Conduct
- I want to work on this issue
- Dominant language
- TypeScript
- Stars
- 101
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from AOSSIE-Org/InPactAI
-
UI Bug: Low contrast makes input text unreadable in Sign Up and Login formPossibly taken @Abhik-Mudi claimed this 309 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AOSSIE-Org/InPactAI#218 ·
-
DOCS UPDATE: Fix incorrect .env file location in Backend Setup instructionsPossibly taken @PulkitDadwal claimed this 323 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 68/100
AOSSIE-Org/InPactAI#201 ·
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
AOSSIE-Org/InPactAI#314 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
AOSSIE-Org/InPactAI#312 ·
-
FEATURE REQUEST: Add API Pagination to Backend List EndpointsMay be free again @alphacoder-hash claimed this 195 days ago, and no pull request is open. Open
Difficulty 4/5 3-5 days Newbie friendliness 50/100
AOSSIE-Org/InPactAI#307 · 2 comments ·
All issues in AOSSIE-Org/InPactAI
Similar issues
-
bug cli service
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
create-element: same editorAlias silent-fallback bug as #201, not covered by that fixPossibly taken A pull request linked to this issue is open or already merged. Opengenerated-by-ai
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
umbraco/Umbraco-CMS-MCP-Editor#208 · 1 comment ·
Maintainers usually reply within 1 day
-
Table: Space fires onActivate in single-selection mode — the reference doc and the JSDoc disagreeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sidorares/react-x11-components#764 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
backnotprop/plannotator#1840 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JoviDeCroock/pracht#432 ·
Maintainers usually reply within 1 day