forked from fiatjaf/coisas
-
Notifications
You must be signed in to change notification settings - Fork 0
/
preferences.js
145 lines (129 loc) · 6.37 KB
/
preferences.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
const load = require('fetch-js')
/* preferences */
const defaultPreferences = {
// most functions must return Promises.
// this function defines how the customization file will be loaded
// from the repository that is being edited. It doesn't make sense
// to change it unless you're hosting your own version of coisas.
loadPreferences: ctx => new Promise((resolve, reject) => {
let repoSlug = `${ctx.params.owner}/${ctx.params.repo}`
load(`https://rawgit.com/${repoSlug}/master/coisas.js`, resolve)
}),
// if you wanna use the default authorizationInit function, but with
// a different endpoint -- you should perhaps fork the default endpoint
// at Glitch and run your own, with your own API keys --, you can just
// modify this URL.
authorizationURL: 'https://steadfast-banana.glitch.me/auth',
// this is the function that will be called when the user clicks at the
// 'authorize with GitHub" button in the navbar. It should somehow fetch
// a token and store it in the browser, or in memory, so it can be fetched
// later with authorizationLoad and deleted with authorizationRemove.
// the token doesn't have to be an OAuth token, it may be a GitHub Personal
// User Token, or a basic token made from username and password.
authorizationInit: () => new Promise((resolve, reject) => {
let popup = window.open(window.coisas.authorizationURL)
window.addEventListener('message', e => {
let parts = e.data.split(':')
let type = parts[0]
if (type === 'authorizing') {
popup.postMessage('send me the token!', window.coisas.authorizationURL)
return
}
let status = parts[2]
let content = JSON.parse(parts.slice(3).join(':'))
if (status === 'success') {
localStorage.setItem('gh_oauth_token', content.token)
resolve()
} else {
console.error(content)
reject()
}
popup.close()
})
}),
// this function is called every time a call is going to be made to
// the GitHub API. It must return a Promise to the full content of the
// 'Authorization' header that will be sent to GitHub.
// You can almost safely return a rejected promise for GET calls, but
// since GitHub may rate-limit you and for all PUT requests a valid header
// is required it is better if you can return a valid header always.
authorizationLoad: (method) => new Promise((resolve, reject) => {
let storedToken = localStorage.getItem('gh_oauth_token')
if (storedToken) return resolve('token ' + storedToken)
else reject()
}),
// called when the user clicks on 'logout'. should remove the token if it
// is stored in the browser or in memory.
authorizationRemove: () => new Promise((resolve) => {
localStorage.removeItem('gh_oauth_token')
resolve()
}),
// called every time the user clicks at "+ new file". should return
// an object with name, content and metadata, these values will be the
// default values for the file that is being crated (or you can just
// return everything empty and the new potential file will have no default
// values, it doesn't mean much).
defaultNewFile: (dirPath) => Promise.resolve({
name: `new-article-${parseInt(Math.random() * 100)}.md`,
content: '~ write something here.',
metadata: {
title: 'New Article',
date: (new Date()).toISOString().split('T')[0]
}
}),
// which files will appear at the left tree. use it to exclude files you
// don't want to edit in the CMS, like code, or binary files.
// the tree is an array of file definitions which will call .filter()
// on this function.
// see https://developer.github.com/v3/git/trees/#get-a-tree-recursively
// to know what the 'tree' is exactly.
filterTreeFiles: file => true,
// the path to a directory into which all files uploaded through the sidebar
// upload widget will be placed.
defaultMediaUploadPath: 'media',
// if set, a link to the live site will appear in navbar.
liveSiteURL: null,
// for each file opened in the editor you can return true or false here
// to determine if the Edit/Preview buttons will be displayed or not.
canPreview: (
path /* this is the relative path of the file in the repo, like '_posts/hi.md' */,
ext /* the file extension, like '.md' */,
isnew /* true if the file is not on the repo, but just being created now */
) => false,
// this function takes a raw HTMLElement and a context object with basically all
// the data the editor has and must render something to that element (for example,
// using `element.innerHTML = 'something'`).
// you probably cannot replicate your entire static website generator in this
// single Javascript function, and you'll also will be in trouble if you need
// to access the contents of all the other pages in the site (for example, if
// you were trying to generate a preview of an index page that shows excerpts),
// but for blog posts and basic content pages you can do a fine job here. also,
// for complicated pages you can probably use fake content where it is missing.
generatePreview: (element, {
path /* the relative path of the file being rendered, like '_posts/hi.md' */,
name /* the filename, like 'hi.md' */,
ext /* the file extension, like '.md' */,
mime /* the mimetype, based on the extension, like 'text/x-markdown' */,
content /* the raw, written content (without frontmatter) */,
metadata /* an object with the metadata, if any, taken from the frontmatter */,
repo /* the current GitHub repository slug, like 'fiatjaf/coisas' */,
tree /* a list of the files in the site, as returned by
https://developer.github.com/v3/git/trees/#get-a-tree-recursively */,
edited /* an object with all the current edited, probably still unsaved,
file contents and metadata, keyed by their path. if a file has
been opened and edited in this current session of _coisas_, it will
be here, otherwise it won't.
like {_posts/what.md: {content: "nada", metadata: {title: "What?"}}}
*/
}) => {}
}
// module loading side-effects are great.
if (window.coisas) {
// someone have injected his preferences directly.
// this must mean coisas is being hosted somewhere
window.coisas = {...defaultPreferences, ...window.coisas}
} else {
// no settings found, we will fetch the settings
// loader from the chosen repository.
window.coisas = defaultPreferences
}