|
3 | 3 | exports[`should return simplify list 1`] = `
|
4 | 4 | Array [
|
5 | 5 | Object {
|
| 6 | + "firstPublishedAt": 1501225933707, |
| 7 | + "subtitle": "減少 Monorepo CI 所需花費時間", |
6 | 8 | "title": "使用 CircleCI 2.0 Workflows 挑戰三倍速",
|
7 |
| - "updatedAt": 1501469016352, |
8 | 9 | "url": "https://medium.com/@username/使用-circleci-2-0-workflows-挑戰三倍速-9691e54b0ef0",
|
9 | 10 | },
|
10 | 11 | Object {
|
| 12 | + "firstPublishedAt": 1499912011732, |
| 13 | + "subtitle": "使用 Redux-Cylces 實行錯誤集中處理", |
11 | 14 | "title": "Centralized Error Handle in React with RxJS",
|
12 |
| - "updatedAt": 1501559328163, |
13 | 15 | "url": "https://medium.com/@username/centralized-error-handle-in-react-with-rxjs-fac9e9e37e44",
|
14 | 16 | },
|
15 | 17 | Object {
|
| 18 | + "firstPublishedAt": 1499671540298, |
| 19 | + "subtitle": "Landing Page for MCS Lite", |
16 | 20 | "title": "React Stack 開發體驗與優化策略",
|
17 |
| - "updatedAt": 1502118302072, |
18 | 21 | "url": "https://medium.com/@username/react-stack-開發體驗與優化策略-b056da2fa0aa",
|
19 | 22 | },
|
20 | 23 | Object {
|
| 24 | + "firstPublishedAt": 1495693600421, |
| 25 | + "subtitle": "Lazy Load React Component with React-Loadable", |
21 | 26 | "title": "Component-based Code Splitting",
|
22 |
| - "updatedAt": 1500651808870, |
23 | 27 | "url": "https://medium.com/@username/component-based-code-splitting-70aeebbb2dc7",
|
24 | 28 | },
|
25 | 29 | Object {
|
| 30 | + "firstPublishedAt": 1494422818494, |
| 31 | + "subtitle": "以一個簡單到不行的大小寫為例,不單只是 Coding Style 或命名規範,你可能會需要 Eslint 來幫你盡量降低這種小意外的發生。", |
26 | 32 | "title": "這個雷踩了四次,為什麼你可能需要 Eslint",
|
27 |
| - "updatedAt": 1501491755288, |
28 | 33 | "url": "https://medium.com/@username/這個雷踩了四次-為什麼你可能需要-eslint-9330c1245ec1",
|
29 | 34 | },
|
30 | 35 | Object {
|
| 36 | + "firstPublishedAt": 1493908671942, |
| 37 | + "subtitle": "Recently, I have read an article by José M. Pérez about How Medium does progressive image loading, and that is what I need about the lazy…", |
31 | 38 | "title": "Reproducing Medium Style Progressive Image Loading for React",
|
32 |
| - "updatedAt": 1501145571134, |
33 | 39 | "url": "https://medium.com/@username/reproducing-medium-style-progressive-image-loading-for-react-2e83bba0c608",
|
34 | 40 | },
|
35 | 41 | Object {
|
| 42 | + "firstPublishedAt": 1493193304597, |
| 43 | + "subtitle": "MCS Lite’s Front-End Tech Stack for Mobile", |
36 | 44 | "title": "Build A Web App in MediaTek",
|
37 |
| - "updatedAt": 1502104016925, |
38 | 45 | "url": "https://medium.com/@username/build-a-web-app-in-mediatek-61b0a26215a0",
|
39 | 46 | },
|
40 | 47 | Object {
|
| 48 | + "firstPublishedAt": 1493083372209, |
| 49 | + "subtitle": "開發板の隨手筆記 - 封裝 MCS API for Arduino", |
41 | 50 | "title": "Writing a Library for LinkIt 7697",
|
42 |
| - "updatedAt": 1494514540173, |
43 | 51 | "url": "https://medium.com/@username/writing-a-library-for-linkit-7697-9e562d28e17",
|
44 | 52 | },
|
45 | 53 | Object {
|
| 54 | + "firstPublishedAt": 1492745328047, |
| 55 | + "subtitle": "多國語言的機制建議盡量在專案初期就能有好的規劃,不至中後期要把字串抽出將會是件累人的事,而在現今前端開發的演進下,多國語言的流程也出現了一些不同的處理方式,以下簡介我們在 MediaTek 內前端專案處理的模式。", |
46 | 56 | "title": "I18n Workflow for React Project",
|
47 |
| - "updatedAt": 1502091407846, |
48 | 57 | "url": "https://medium.com/@username/i18n-workflow-for-react-project-9f9ff8fe9aef",
|
49 | 58 | },
|
50 | 59 | Object {
|
| 60 | + "firstPublishedAt": 1492590593069, |
| 61 | + "subtitle": "Prettier v1.0.0 就在四月初已經正式釋出,等同宣稱在 Production 環境也可安心穩定地使用了,也是時候考慮導入至專案中囉。在專案的導入順序我想應該會是 Prettier 再來才是 Eslint 的設定,兩者是可以並存的,以下以我覺得的導入順序做介紹。", |
51 | 62 | "title": "Introducing Prettier with Eslint",
|
52 |
| - "updatedAt": 1501264734071, |
53 | 63 | "url": "https://medium.com/@username/introducing-prettier-with-eslint-13f567ae0184",
|
54 | 64 | },
|
55 | 65 | ]
|
|
0 commit comments