Proposed Example Outline
- Dominant language
- JavaScript
- Stars
- 346
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
I propose we craft a simple example that de-constructs/re-creates the _basic_ GitHub application.
We can _model_ the _basic_ GitHub interface quite easily:
+ [x] Users
+ [x] Profile
+ [x] Name
+ [x] Username
+ [x] uid (_the person's unique **numeric** id e.g: `4185328`_)
+ [x] etc. see: https://github.com/nelsonic/github-scraper#profile-page
+ [x] Repositories
+ [x] Stars
+ [x] Followers
+ [x] Following
+ [x] Organisations
+ [x] Members (_an org can have have zero or more/many members_)
+ [x] Repositories
> **Note**: For now we will deliberately leaving out the "Projects", "Wikis" and Pull Requests for now.
We can _add_ these things in later if desired (_or if readers/learners request them!_). But _for now_, we don't _need_ them in order to explain the _concept_ of relational data.
# Todo
+ [x] Write "raw" SQL Statements to **`CREATE`** the tables with relationships e.g: [database_setup.sql](https://github.com/nelsonic/time-mvp/blob/747c050032402d040fea4d717aae2ee84e2bac64/server/database_setup.sql)
+ [ ] Create a _sample_ application using SQL statements (no ORM) to allow people to download the code and _run_ it locally to "hack" on it and learn more.
For a _detailed example_ of what I have in mind, see: https://github.com/dwyl/todo-list-javascript-tutorial
Related to #21 & #23 where Jack _requested_ having a simple example.
_Also_ related to #3 as our example _needs_ to have a relational data diagram.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.