solidusio / solidusio/solidus_auth_devise
Shouldn't order history be inside solidus repo?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 56
- Forks
- 124
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 1
Description
Hello, I am integrating Solidus ecommerce in an existing app, so I need to use the existing User table.
I am not actually using this gem, but I found out that the user orders history (routes, views and so on) are inside this repo.
I am a bit confused about it, because authentication does not really concern orders, IMHO these parts of code may better belong inside solidus codebase. What's your opinion on this matter?
Contributor 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.
Research direction
Start by reviewing the order-history routes and views mentioned in the issue, along with the repository’s authentication responsibilities. Determine whether those components belong in solidus_auth_devise or the Solidus codebase, then seek a maintainer decision; the issue does not define an implementation or a concrete done state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- authentication, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100