feat: Run zmd client side #268

Heziode · 2018-08-19T13:55:52Z

This PR aims at providing a client-side bundle of zmarkdown.

Related to #259

Note: This is currently a Work In Progress

Client Architecture

The architecture of the client is similar to remark or Vue. The manager, here client/client.js, exposes the variable ZMarkdown. This manager doesn't work alone because it does not know how to convert the input to the desired output. Example, if you want to convert markdown to html, the manager doesn't know how to do this. It need modules to know how to do this.

Manager

You need to add modules with ZMarkdown.use(obj) to manage rendering.

To convert a markdown string you should use ZMarkdown.render(str, moduleName = null, cb = null):

str: string, string to convert
moduleName: string, name of the module you want to use. This parameter can be omitted only if you define a default module with ZMarkdown.setDefaultModule (you can reset default type with ZMarkdown.resetDefaultModule)
cb: function(err, vfile), called when process is done

This function return a Promise if no callback specified.

ZMarkdown have also a parse(moduleName) function to get the MDAST tree and getParser(moduleName) to get the whole parser. This parameter can be omitted only if you define a default module with ZMarkdown.setDefaultModule.

Module

The module is an object that should have the following properties:

name: string, a string that define the name of the plugin. This is used to identify each plugins
render: function(input, cb): void, a function called in ZMarkdown.render. It returns a Promise if no callback specified
parse: function(input): object, get MDAST tree
getParser: function(): object, get the whole of parser
initialize: function(config), configure the module with a custom configuration. You do not have to call this function if you want to use the default configuration

Tips

You can start a module with a base parser using ./common.js. The module exports a function that can take two optionals parameters:

opts: an object that can have:
- remarkConfig: object , your remark config (defaults to the configuration from config/remark)
- extraRemarkPlugins: array of objects, remark plugins you want to add to the default parser (remark pipeline). The object should contain:
  - obj: remark plugin
  - option: optional, option of the plugin
  - check: function(config) optional, a function that returns a boolean to use this plugin depending to remark config passing in argument of common
processor: function(config) (default getHTMLProcessor of ./common.js), processor function used to configure the remark pipeline for you output

Module example:

const common = require('../../common') /* zmarkdown common file */
const remarkToc = require('remark-toc')
const remark2rehype = require('remark-rehype')

const opts = {
  remarkConfig: null /* custom remark config. Null or omit to use default conf */,
  extraRemarkPlugins: [
    {
      obj: remarkToc,
      option: null /* remark plugin option. Null or omit to not configure it */,
      check: (config) => {
        /* 
         * This function allow to use this plugin only on certain cases. 
         * The config passed in argument are remark config.
         *
         * Note: This config are the config passed in opts when 
         * instancing common. Common make a clone of this conf, thereby
         * any update make after instancing common will not apear.
         * For example, the "noTypography" define in processor function
         * below not appear in this conf.
         */
        return true
      },
    },
  ],
}

const processor = (config) => {
  config.remarkConfig.noTypography = true

  return globalParser.zmdParser(config.remarkConfig, config.extraRemarkPlugins)
    .use(remark2rehype, config.remarkConfig.remark2rehype)
}

const globalParser = common(opts, processor)

export function render (input, cb) {
  return globalParser.render(input, cb)
}

export function parse (input) {
  return parser.parse(input)
}

export function getParser () {
  return parser
}

export const name = 'custom-html'

Modules need to be bundled for used on the client.

Here is a webpack conf of the previous example:

const path = require('path')

const mode = process.env.NODE_ENV ? process.env.NODE_ENV : 'production'

module.exports = {
    mode,
    name: 'ZMarkdownCustomHTML', // name of process if you use parallel-webpack
    entry: ['./plugins/client/custom-html'], // path to your module
    output: {
      path: path.resolve(__dirname, 'dist'), // destination folder
      filename: 'custom-html.js', // file name
      library: 'ZMarkdownCustomHTML', // Name of the global constant for dom access
    },
    module: {
        rules: [
          {
            test: /\.js$/,
            exclude: /(node_modules|bower_components)/,
            use: {
              loader: 'babel-loader',
            },
          },
        ],
    },
}

What was done

Modular client-side convert
ZesteDeSavoir HTML plugin
(Optional) ZesteDeSavoir Latex plugin
Investigate trouble with youtube video (remark-iframes): Uncaught (in promise) TypeError: URLSearchParams is not a constructor
Update reamde of zmarkdown package to add client description (present in this PR description)

Todo

houndci-bot · 2018-08-19T13:56:01Z

packages/zmarkdown/client/script.js

+  minSize: 200
+})
+
+// console.log("zmdParser: ", zmdParser);


Irregular whitespace not allowed no-irregular-whitespace

houndci-bot · 2018-08-19T13:56:01Z

packages/zmarkdown/client/script.js

@@ -0,0 +1,6 @@
+Split(['#left', '#right'], {
+  sizes: [50, 50],
+  minSize: 200


Missing trailing comma comma-dangle

houndci-bot · 2018-08-19T13:56:01Z

packages/zmarkdown/client/script.js

@@ -0,0 +1,6 @@
+Split(['#left', '#right'], {


'Split' is not defined no-undef

vhf · 2018-08-26T13:38:18Z

@Heziode Any progress here?

Some guidance:

The client-side zmarkdown entrypoint needs a different config from it's server-side counterpart
- remove remark-images-download: the client shouldn't download images found in the markdown source
- remove rebber and its deps: the client doesn't need to generate LaTeX source (at least in a first iteration ; LaTeX source preview might be a fun addition in the future but has very low priority since we don't need it for our use case)

Heziode · 2018-08-26T14:40:26Z

No progress, I do not have a lot of time.
I will be able to devote myself entirely for this from Tuesday.

Heziode · 2018-08-28T11:05:49Z

Instead of remove image download and latex transpiler, can we use an "plugin" architecture like Vue.js, remark and Cie ? Like that we can allow user (developer) to use what it want.

vhf · 2018-08-28T11:38:07Z

Yes, all we currently have is plugins. You still need to remove image downloads because browsers don't have access to the filesystem.

Heziode · 2018-08-28T12:04:37Z

Ok, I will do that.

client html can load plugins. Example plugin can be found in `plugins/client/zhtml.js`

houndci-bot · 2018-08-28T16:46:21Z

packages/zmarkdown/zmdParser.js

+      })
+
+      // get a unique list of languages used in input
+      const languages = new Set()


'Set' is not defined no-undef

houndci-bot · 2018-08-28T16:46:22Z

packages/zmarkdown/plugins/client/zhtml.js

+  const mdProcessor = getHTMLProcessor()
+
+  if (typeof cb !== 'function') {
+    return new Promise((resolve, reject) =>


'Promise' is not defined no-undef

Heziode · 2018-08-28T16:48:23Z

@vhf Can you "pre-review" the code (for the structure) and tell me if you agree with this ?
I will "clean code" and add tests later.

vhf

Definitely a good start 👍

Could you please ignore the path packages/zmarkdown/dist/? No need to have these at this point

vhf · 2018-08-28T16:56:31Z

packages/zmarkdown/index.js

@@ -49,6 +28,8 @@ const rebberStringify = require('rebber/src')
 const remarkConfig = require('./config/remark')
 const rebberConfig = require('./config/rebber')

+const zParser = require('./zmdParser')


Could you please use kebab-case for filenames (here parser would be fine) and name the variable parser as well? (see other comment about this file)

vhf · 2018-08-28T17:00:07Z

packages/zmarkdown/plugins/client/zhtml.js

+
+const rehypeStringify = require('rehype-stringify')
+
+const jsFiddleAndInaFilter = node => {


Most of this file seems duplicated from the other one. What would you think of factoring the common parts out in a file that would define all of these utilities and exports them separately? (This file would also replace zmdParser.js)

// …requires // …definitions module.exports = { foo, bar, baz }

that's what I meant by "clean code", refactor code.

To me this would be a structural change, not a minor cleanup. Would you do it that way or what are your thoughts?

I have a little idea of how to do that. I will do that tomorrow.

vhf · 2018-08-28T17:03:09Z

packages/zmarkdown/.babelrc

@@ -0,0 +1,9 @@
+{
+  "presets": ["env"],


Please add targets in here

How do you want to configure that ? I do not have any idea of how to configure that.

I'd say > 0.5%, last 2 versions, Firefox ESR, not dead, ie >=11

vhf · 2018-08-28T17:04:13Z

packages/zmarkdown/client/index.js

+  }
+
+  // Check the object structure
+  if (!('name' in obj)) {


Don't use in to check for the presence of a key, prefer hasOwnProperty (same for the rest of the file)

~~Can you please explain why use hasOwnProperty instead of in ?~~

Ok, I have my answer with The Uses of 'in' vs 'hasOwnProperty'.

It's more precise and corresponds better to what we want to achieve here. We don't care about a method obj.name() (i.e. YourObjectsPrototype.prototype.name) for instance, what we're looking for is a property.

vhf · 2018-08-28T17:04:28Z

packages/zmarkdown/client/index.js

+  // Check the object structure
+  if (!('name' in obj)) {
+    throw new Error("missing 'name' in plugin")
+  } else if (typeof obj.name !== 'string') {


else is useless here (same for the rest of the file)

packages/zmarkdown/client/index.js

In `render` function, add possibility to use callback in the second parameter by omitting 'type' parameter. In 'use', we check if the parameter is an object.

vhf · 2018-08-29T10:57:16Z

packages/zmarkdown/client/index.js

+      if (!cb) {
+        cb = type
+      } else if (typeof cb === 'function') {
+        throw new Error("Non deterministic use of cb due to type of 'type' and type of " +


Extra args are always allowed in JavaScript, we should silently ignore this case.

packages/zmarkdown/client/index.js

houndci-bot · 2018-09-05T06:48:47Z

packages/zmarkdown/common.js

+    const mdProcessor = getHTMLProcessor(remarkConfig, extraPlugins)
+
+    if (typeof cb !== 'function') {
+      return new Promise((resolve, reject) =>


'Promise' is not defined no-undef

packages/zmarkdown/common.js

Heziode · 2018-09-05T09:54:45Z

@vhf,

The feature is globally complete, but, I have some trouble with tests. I do not understand why it not pass. And now the "inspect" break the object.

vhf · 2018-09-05T18:24:01Z

Nice!

Take a look at the logs: https://travis-ci.org/zestedesavoir/zmarkdown/jobs/424714133 , I'm sure you'll find out why tests are failing.

@Heziode I'm pretty sure that by reading the diff while doing this review I found the bug you're looking for. See comments below

vhf · 2018-09-05T18:25:37Z

.babelrc

@@ -5,5 +5,6 @@
    "development": {
      "sourceMaps": "inline"
    }
-  }
+  },
+  "targets": "> 0.5%, last 2 versions, Firefox ESR, not dead, ie >=11"


This config should be in https://github.com/zestedesavoir/zmarkdown/pull/268/files#diff-3073df2720eaad6e9a1b54da7f5aab4b

Bad link ? I do not know where you want me to put it.

Ok, my bad, I have understood.

packages/zmarkdown/client/index.js

Ignore css files generated by zds-site

…re built

vhf · 2018-09-24T19:30:54Z

Good progress. Could you please remove codacy (we don't use it in this project) and update the README?

After that I'll try this PR again locally (building it using the instructions you'll provide), do a last round of review and we'll be good to go.

Heziode · 2018-09-25T07:57:39Z

It is done.

Due to portage of remark-iframes from python version. In python the parameter feature was deleted from URL. This cause trouble on the client.

Heziode · 2018-09-27T09:49:56Z

@vhf if you don't use codacy for this project, can you disable it ? It fails the PR.

artragis · 2018-09-27T14:18:56Z

oups, my bad.

vhf

Thanks @Heziode , looking really good!

vhf · 2018-09-28T11:23:04Z

packages/zmarkdown/common.js


-function getLatexProcessor (remarkConfig, rebberConfig, target) {
-  remarkConfig.noTypography = true
+  if (extraRemarkPlugins && extraRemarkPlugins.length > 0) {


I think you could remove this condition if you do const zmdParser = (config, extraRemarkPlugins = []) => { on l.70.

vhf · 2018-09-28T11:28:16Z

packages/zmarkdown/common.js

+  if (extraRemarkPlugins && extraRemarkPlugins.length > 0) {
+    for (const record of extraRemarkPlugins) {
+      if (!record.check || record.check(config)) {
+        if (record.option) {


In the README you wrote that passing null as option means no configuration for the plugin. Is this really what we want? What if a plugin has a default config and passing null disables it? In this case we couldn't pass null.

I think there is some confusion between the semantics of null and undefined. A missing config would be undefined, it would use a default value if any. Explicitly passing null should still be possible.

Some remark plugin doesn't have config. The null is for these plugins

I still think this condition is incorrect. I think you are confusing null with undefined.

Imagine the following plugin:

(config) => { if (typeof config === 'undefined') config = defaultConfig // this is basically (config = defaultConfig) => {} doSomething(config) }

How do I pass null to doSomething? (if (record.option) will be false when record.option === null, which is why this condition is not correct.)

In other words: the config should be undefined unless you define some config.

Defining the config as null means that null is the config, it is defined as null and therefore it is not undefined.

There are plenty of other cases.

if (config) useConfig(config) doesn't let you use null or false or 0 or '' as config. All of these values could be used by plugins authors.

Indeed, I have do the change.

packages/zmarkdown/common.js

vhf · 2018-09-28T11:33:55Z

packages/zmarkdown/config/remark.js

@@ -29,6 +29,7 @@ const remarkConfig = {
    blocks: [],
  },

+  canUseTextr: true,


I'd prefer something like useTextr or enableTextr or (with the value as false) disableTextr. It's not that this option let's us decide later whether we want to use textr or not, this option explicitly enables it.

vhf · 2018-09-28T11:35:44Z

packages/zmarkdown/server.js

+function rendererFactory (config, target) {
+  if (target === 'html') {
+    return zmd.rendererFactory(config)
+  } else if (target === 'latex') {


It seems to me that else is useless here?

Heziode · 2018-09-30T18:00:28Z

I do review change asap.

vhf · 2018-09-30T22:05:29Z

Apparently there's no way for me to remove @codacy. Nothing I can do from this repo settings panel, clicking on the failed @codacy check redirects me to a login page where this service wants me to give it access to my github profile, which I'll never allow.

artragis · 2018-10-01T09:20:36Z

Logicaly, on zmarkdown this should be fine as no other member would have set it up. The currrent "failure" was due to the fact I, one day, added zmarkdown in my own codacy dashboard. I removed it, so on next commit my "codacy warning" won't show up.
I clearly agree : codacy is broken.

vhf · 2018-10-03T18:57:27Z

packages/zmarkdown/common.js

@@ -213,7 +211,7 @@ module.exports = (
    opts = {}
  }

-  if (!opts.remarkConfig || (opts.remarkConfig === null) || !Object.keys(remarkConfig).length) {
+  if ((opts.remarkConfig === null) || !opts.remarkConfig || !Object.keys(remarkConfig).length) {


See #268 (comment)

vhf · 2018-10-03T19:03:47Z

packages/zmarkdown/common.js

+  if (extraRemarkPlugins && extraRemarkPlugins.length > 0) {
+    for (const record of extraRemarkPlugins) {
+      if (!record.check || record.check(config)) {
+        if (record.option) {


I still think this condition is incorrect. I think you are confusing null with undefined.

Imagine the following plugin:

(config) => { if (typeof config === 'undefined') config = defaultConfig // this is basically (config = defaultConfig) => {} doSomething(config) }

How do I pass null to doSomething? (if (record.option) will be false when record.option === null, which is why this condition is not correct.)

packages/zmarkdown/common.js

vhf

Could you please add some build instructions to the README?

How to get the live reload dev build mode?
How to build a production bundle, minified etc?

packages/zmarkdown/README.md

vhf · 2018-10-04T08:54:19Z

packages/zmarkdown/public/index.html

+  <pre class="result render latex-result">
+  </pre>
+</div>
+<script src="../dist/zmarkdown.js"></script>


This will be an issue to deploy to github pages because this file will be at the root of the branch.

I suggest to delete the current root public symlink and creating a symlink from here ./js -> ../dist (or ./dist). In the travis deploy script I'll then copy the content before pushing.

Here would be the travis config:

git: depth: 10 language: node_js cache: directories: - node_modules node_js: - '8' - '10' env: - DEST=/tmp global: secure: V3Wlrzc7mpyVxNxeBPMkfyowycurM2OmkTTc3aeUkRjrdltRNfknudhC2OELSpsfMvUTLLSPW/oMfv+jxgVHOydVIsBbN+lB0jKnm/T+ABfUeDw+tpEEvKvKLtD/uxDB3rC83uD9ociE82PqdGYtBOJX4Sug5bdoq8n02DlsGd1dnsr1dIdIIX0LHp4OkfRF6jv0EyXwSHK7Kk6s/miPtuChHrhJQwsjJBu5YPdSEu+f0mzilEO5NUiv4hT1IWjfBravP6uTyWIUcwtfY1rgmjZy3d+MaCRKbLi4hrzrIa/VL/rX9fg8vN6Jgnt1+kJtPB7Y0yH2tcl0tpeRWW2ppBZOUU2rJ5OWA8TKltZZW7zjQgrdrwNns0+8ifZ7AI/Jdfvfj0NjW/SqsxchLQL2uN0FsBkoUV6Ly4cwZ/B5EIFTdi0qnjcYBdHoXE21j81clk0rKdgiof/lGOL4+bA59O7V88AEOmgGshRF1AUbe1SwBQ6l8+w44ZDg7I9OQfNSf/W07NbT4cwSF+xp4nc0Rw0EzHnfHLxdYv0Dj+1GxAQdtJ22wmN5JFKlENsfslC6bHT2ZN2V5U0K2VqCBdh0iNdV/uV9tdy3GCSnO3W2XuBKtDbo+wrLf8rjIubWwupej8JxR+pPJ10KNJN5rhe/pqIRujr5FxUZJG7mll9w9Ws= before_install: - npm install -g pm2 install: - npm install - npm run bootstrap before_script: - pm2 ping after_success: - cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js - rm ./packages/zmarkdown/public/js - cp ./packages/zmarkdown/dist/* ./packages/zmarkdown/public/js/ deploy: provider: pages skip-cleanup: true github-token: "$GITHUB_TOKEN" keep-history: false target-branch: gh-pages local-dir: ./packages/zmarkdown/public on: branch: master

If I well understood what was asked, it's good now.

vhf

Thanks for all your hard work on this!

Heziode added 2 commits August 19, 2018 15:50

feat(client-side): Add conf to build zmd for client side

c6410d7

feat(client-side): Add simple HTML page for POC

d68b4a1

houndci-bot reviewed Aug 19, 2018

View reviewed changes

Heziode changed the title ~~WIP: Feature/run zmd client side~~ WIP: Run zmd client side Aug 19, 2018

feat(client-side): Add client structure

8d4b22a

client html can load plugins. Example plugin can be found in `plugins/client/zhtml.js`

houndci-bot reviewed Aug 28, 2018

View reviewed changes

vhf reviewed Aug 28, 2018

View reviewed changes

Heziode added 4 commits August 29, 2018 11:09

chore: Re-add gitignore and ignore dist folder

c43cc21

chore: Update code due to code review changes

78c5473

chore: Add check in use and render function

b0098f0

In `render` function, add possibility to use callback in the second parameter by omitting 'type' parameter. In 'use', we check if the parameter is an object.

chore: remove ignored files

f7c6aee

vhf reviewed Aug 29, 2018

View reviewed changes

packages/zmarkdown/client/index.js Outdated Show resolved Hide resolved

Heziode added 2 commits September 5, 2018 08:45

chore: Factorize common code used in both side (client and server)

30b4a52

chore: add target attribute to babel conf

a8a4b05

houndci-bot reviewed Sep 5, 2018

View reviewed changes

Heziode added 4 commits September 5, 2018 08:59

chore: update zmarkdown reference in tests

ad0c178

style(lint): Add global eslint conf for Set and Promise in common file

e3ff637

chore(test): fix bad parameter for renderString

19619ef

chore(test): attempt to fix tests on server

ebe3d07

vhf reviewed Sep 5, 2018

View reviewed changes

packages/zmarkdown/client/index.js Show resolved Hide resolved

Heziode added 6 commits September 10, 2018 16:03

chore: Add spoiler mechanism in POC

ab0fc36

style(css): Update style of POC

b2d4b31

ci(codacy): Add config file

af315dd

Ignore css files generated by zds-site

chore: Add missing spoiler-build style class when spoiler mechanism a…

e4d4531

…re built

chore: update style and add spoiler in default editor value

882c332

chore: Fix exclude_paths in codacy config

ef044eb

Heziode added 2 commits September 25, 2018 09:16

chore: Update README

8348639

chore: remove codacy config

b5186dd

Heziode added 2 commits September 25, 2018 10:19

fix(remark-iframes): Fix youtube link client side

6b2e960

Due to portage of remark-iframes from python version. In python the parameter feature was deleted from URL. This cause trouble on the client.

chore(zmd-client): re-add youtube link

2284b64

vhf reviewed Sep 28, 2018

View reviewed changes

chore: Update code due to code review changes

454dcdf

vhf reviewed Oct 3, 2018

View reviewed changes

vhf requested changes Oct 3, 2018

View reviewed changes

packages/zmarkdown/common.js Outdated Show resolved Hide resolved

chore: Update code due to code review changes

c7a20da

Heziode changed the title ~~WIP: Run zmd client side~~ feat: Run zmd client side Oct 4, 2018

vhf requested changes Oct 4, 2018

View reviewed changes

packages/zmarkdown/README.md Show resolved Hide resolved

vhf requested changes Oct 4, 2018

View reviewed changes

Heziode added 2 commits October 4, 2018 13:00

chore: Update code due to code review changes

f636dc8

chore: Update public dir

14ef3a1

vhf approved these changes Oct 4, 2018

View reviewed changes

vhf merged commit 057e6e9 into zestedesavoir:master Oct 4, 2018

Heziode deleted the feature/run-zmd-client-side branch October 4, 2018 16:14


		const rehypeStringify = require('rehype-stringify')

		const jsFiddleAndInaFilter = node => {

feat: Run zmd client side #268

feat: Run zmd client side #268

Conversation

Heziode commented Aug 19, 2018 • edited Loading

Client Architecture

Manager

Module

Tips

What was done

Todo

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

vhf commented Aug 26, 2018

Heziode commented Aug 26, 2018 • edited Loading

Heziode commented Aug 28, 2018

vhf commented Aug 28, 2018

Heziode commented Aug 28, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Heziode commented Aug 28, 2018 • edited Loading

vhf left a comment • edited Loading

Choose a reason for hiding this comment

vhf Aug 28, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Heziode Aug 29, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Heziode Aug 28, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Heziode commented Sep 5, 2018

vhf commented Sep 5, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

vhf commented Sep 24, 2018

Heziode commented Sep 25, 2018

Heziode commented Sep 27, 2018

artragis commented Sep 27, 2018

vhf left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

vhf Oct 3, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Heziode commented Sep 30, 2018 • edited Loading

vhf commented Sep 30, 2018 • edited Loading

artragis commented Oct 1, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

vhf left a comment

Choose a reason for hiding this comment

vhf Oct 4, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

vhf left a comment

Choose a reason for hiding this comment

Heziode commented Aug 19, 2018 •

edited

Loading

Heziode commented Aug 26, 2018 •

edited

Loading

Heziode commented Aug 28, 2018 •

edited

Loading

vhf left a comment •

edited

Loading

vhf Aug 28, 2018 •

edited

Loading

Heziode Aug 29, 2018 •

edited

Loading

Heziode Aug 28, 2018 •

edited

Loading

vhf commented Sep 5, 2018 •

edited

Loading

vhf Oct 3, 2018 •

edited

Loading

Heziode commented Sep 30, 2018 •

edited

Loading

vhf commented Sep 30, 2018 •

edited

Loading

vhf Oct 4, 2018 •

edited

Loading