rubyforgood / rubyforgood/alongwithyou
Write an ADR for the Rails/Expo architecture boundary
Open
Nobody has claimed this yet.
phase:0
type:foundation
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Record what lives in the API vs. the client, once the architecture decision above is made.
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.
Research direction
The issue names no files or tests; first read the referenced architecture decision above and identify the project’s API and client entry points. Record the Rails/API versus Expo/client boundary in an ADR, with the work complete when the responsibilities of both sides are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, typescript
- Domain
- documentation, full-stack
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 40/100