assemblee-virtuelle / assemblee-virtuelle/semapps
SsoLoginPage: mieux gérer le GET de l'utilisateur
- Dominant language
- TypeScript
- Stars
- 103
- Forks
- 14
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
Pour l'instant, on fait un `getOne` sur une ressource `Person`.
https://github.com/assemblee-virtuelle/semapps/blob/master/src/frontend/packages/auth-provider/src/components/SsoLoginPage.js#L58
Mais les utilisateurs peuvent avoir un autre nom de ressource. Il faudrait que ce soit configurable.
De plus, si la ressource n'existe pas, getOne retourne une erreur mais on ne la prend pas en compte.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/frontend/packages/auth-provider/src/components/SsoLoginPage.js around line 58 and inspect how the Person resource is passed to getOne. Trace the auth-provider configuration to determine where the resource name can be made configurable, then check the existing frontend tests or test setup. Done means alternate resource names work and a missing resource error is handled without an unhandled failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100