max-mapper / max-mapper/monocles
you should be able to have multiple aspects
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 178
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
port over the concept of aspects, or groups of friends and updates from that group
each aspect should store it's messages in a separate database
you should be able to create an aspect from the UI, and it should create a new DB and copy the required views into that new DB in a bootstrap function
a list of aspects that a user is a part of and whether or not should be stored on the user's profile
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
Start by tracing the existing UI flow for creating or editing a user profile and the bootstrap function that creates databases and copies views. Determine how aspects, group updates, and per-aspect databases should integrate with those entry points. Done means users can create aspects from the UI, required views are copied into each new database, messages are separated, and profile membership is stored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100