smpallen99/coherence

Suggestion - unifying the db access routes.

Open

#361 opened on Jul 14, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Elixir (220 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (1,259 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I added some additional function calls to create_user/1, create/1, and create!/1 of schemas.ex.

But it seems that the coherence registration doesn't use schemas.ex functions. I think it's better unifying the db access routes to maintain and modify functionalities.

Is there any plan to use schemas.ex functions?

Contributor guide

Research direction
Explore the coherence codebase to understand how database access is currently handled in schemas.ex and in the registration module. Identify inconsistencies and propose a unified approach using schemas.ex functions.
Tech stack
elixir
Domain
backendauthentication
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ElixirPhoenixGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55