lynndylanhurley / lynndylanhurley/devise_token_auth

null user attributes on email registration

Open
#1,477 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
3.6k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

When a user registers using email, the values sent in JSON are not saved in the user object.

![image](https://user-images.githubusercontent.com/36763164/115957280-a9f6b480-a501-11eb-93eb-02421f0e4b8b.png)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing registration through the email flow using JSON attributes, then inspect where those values should enter the user object. Done means the attributes sent during email registration are present on the created user; no file or test is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
api, authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.