Login/register pages are UI-only stubs, submit does nothing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, backend-api-design, frontend
Research direction
Start with the TODOs at packages/front-end/pages/login.vue:51 and packages/front-end/pages/register.vue:72, then inspect packages/back-end/src/functions/httpFunctions.ts for the absence of an authentication endpoint. Resolve the session-versus-JWT and credential-validation approach first. Done means both forms submit through the chosen auth flow, report errors, and redirect after success.
Written by the indexing model from the issue text.
Description
What's happening
packages/front-end/pages/login.vue:51 and packages/front-end/pages/register.vue:72 both have:
// TODO send user Data to the login endpoint and redirect if successful
with no actual submit handler implementation. Both pages render a full form UI but pressing submit does nothing observable — no request is sent, no error is shown, no redirect happens.
Impact
There is currently no working authentication in the app. This may be intentional (no backend auth endpoint exists yet either), but the pages presenting as functional forms without any indication they're non-functional could confuse users/testers.
Scope
This is a real feature gap, not a bug fix — needs a design decision on the auth approach (session vs JWT, where credentials get validated, etc.) before implementation, so it's filed as a feature request rather than something to silently patch.
Related: no backend endpoint for authentication currently exists in packages/back-end/src/functions/httpFunctions.ts.
- Dominant language
- Vue
- Stars
- 1
- Forks
- 1
- Avg merge
- 58m
- Merged PRs (30d)
- 1
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.
More from helpfulengineering/project-data-platform-ts
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in helpfulengineering/project-data-platform-ts
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sisaku-security/sisakulint#647 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yunaremaia/driftcheck#246 ·
-
bug good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yunaremaia/taintrace#110 ·