See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
| http://sample.vodobox.net/skate_phantom_flex_4k/skate_phantom_flex_4k.m3u8 | |
| http://playertest.longtailvideo.com/adaptive/wowzaid3/playlist.m3u8 | |
| http://cdn-fms.rbs.com.br/vod/hls_sample1_manifest.m3u8 | |
| http://nasatv-lh.akamaihd.net/i/NASA_101@319270/index_1000_av-p.m3u8?sd=10&rebase=on | |
| http://content.jwplatform.com/manifests/vM7nH0Kl.m3u8 |
| [alias] | |
| co = checkout | |
| cob = checkout -b | |
| coo = !git fetch && git checkout | |
| br = branch | |
| brd = branch -d | |
| brD = branch -D | |
| merged = branch --merged | |
| st = status | |
| aa = add -A . |
Express makes it easy to nest routes in your routers. But I always had trouble accessing the request object's .params when you had a long URI with multiple parameters and nested routes.
Let's say you're building routes for a website www.music.com. Music is organized into albums with multiple tracks. Users can click to see a track list. Then they can select a single track and see a sub-page about that specific track.
At our application level, we could first have a Router to handle any requests to our albums.
const express = require('express');