Custom schemas path won't work

[Torrriate]

Any schemas path other than "schemas" will still create the target output folder specified, but will NOT render the respective .html output files there.

I was able to track the problem down to the " rightclick / copy" - script.
Lines 49 to 51 look as follows:

     if (fileSuffix.test(suffix)) {
        clip[docPath] = fs.readFileSync(fullPath, enc);
      }

Before the synchronous file reading operation the object "this.clipboard.files.schemas" contains one schema-path less than after. So somehow this "this.clipboard.files.schemas"-object is getting a local docPath of one of the .json schemas in the "schemas"-folder added at this point, but only if your schemas path is "schemas".
Not so if it is any other custom-path.
Why?

Btw., my jade module is installed globally - if that makes any difference.

[mattyod]

Sorry missed this somehow. Can you show me your .maticrc file?

[Torrriate]

Sorry for the late resumption.

My "matic.rc":

{
  "assets": ["js", "css"],
  "index": false,
  "schemas": {
    "path": "schemaz",
    "suffix": "json",
    "indent": 2
  },
  "target": {
    "path": "web",
    "suffix": "html"
  }
}

the directory "web", as determined by the target-path, is being created. The folder "schemaz" (examplary custom path, other than the schemas-dir as default-wise proposed by you) exists and contains the non-empty json-schema files and thus is copied including them as its content to the web-dir. However, the matic output-hml-files are not being rendered (there or anywhere...). No error is being thrown though!

If however the schemas-path will be set to schemas (back to the default value as proposed by you), the rendering succeeds.

?

Thx!

[Akuryou]

Hi,
I got the same problem with templates in a custom folder.

.matirc:

{
  "assets": ["html/js", "html/css"],
  "index": {
    "schemas": true
  },
  "schemas": {
      "path": "schemas",
      "suffix": "json",
      "indent": 2
  },
  "templates": {
    "folder": true,
    "path": "html/templates",
    "file": "default",
    "lib": "pug",
    "suffix": "pug"
  }
}

The problem seems to be hard coded paths to templates and schemas at several locations
"grep" for this.clipboard.files.schemas or this.clipboard.files.templates and you will get this:

../node_modules/matic/lib/merge.js: subSchema = pointy(this.clipboard.files.schemas, schema, val) ||
../node_modules/matic/lib/merge.js: local(this.clipboard.files.schemas, val, schema);
../node_modules/matic/lib/merge.js: _.each(this.clipboard.files.schemas, function (val, key) {
../node_modules/matic/lib/merge.js: this.clipboard.files.schemas[key] = JSON.stringify(merge(JSON.parse(val), key), null, indent);
../node_modules/matic/lib/index.js: itterate(this.clipboard.files, '', index.files);
../node_modules/matic/lib/utils/compile.js: _.each(this.clipboard.files.templates, function (template, name) {
../node_modules/matic/lib/utils/compile.js: delete this.clipboard.files.templates[name];
../node_modules/matic/lib/utils/compile.js: delete this.clipboard.files.templates;
../node_modules/matic/lib/utils/render.js: .each(this.clipboard.files.schemas, function (schema, name) {
../node_modules/matic/lib/utils/render.js: this.clipboard.files[fileName] = template(schema);
../node_modules/matic/bin/extend.js: if (!.isEmpty(this.clipboard.files)) {
../node_modules/matic/bin/extend.js: _.extend(userConfig, JSON.parse(this.clipboard.files[configFile]));

I'll fork, fix those issues and send you a PR once I'm done.