It is a common use case in Netlify CMS to have sub-objects or lists of sub-objects in Markdown frontmatter. This plugin should convert paths also in arrays, objects, arrays of objects, etc.

Can I make this plugin work with JSON files that NetlifyCMS is creating?
My JSON contains image paths, but this plugin only seems to transform frontmatter.

Hi, I try to use your plugin because I have frontmatter like this:

---
cover: /content/images/sunrise.jpg
---

I have this config:
```js
plugins: [
    "gatsby-plugin-netlify-cms-paths",
    {
      resolve: "gatsby-transformer-remark",
      options: {
        plugins: [
          "gatsby-plugin-netlify-cms-paths",
        ]
     }
  }
]

But I still have the following error when I build:

Field "cover" must not have a selection since type "String" has no subfields.

Am I using your plugin the wrong way?

Thank you

Will this plugin work with gatsby v2?

Is there anyway to get this plugin to work with manual initialization...
https://www.netlifycms.org/docs/beta-features/#manual-initialization

It seems to be looking for the config.yml file, but that wouldn't be used when using manual init.

Description

This plugin stops working for me after updating gatsby to 2.2.0 which introduced the addition of Schema Customization API.

I've confirmed that it still works on 2.1.39.

I suspect this may be OS-related, as my colleague who runs Linux does not have the same issue. I have updated node, npm and gatsby-cli.

Steps to reproduce

I have set up a minimal demo from the default starter: https://github.com/laradevitt/my-default-starter

1. Create a new site from the demo
2. Run gatsby develop or gatsby build

Expected result

The field 'image' should be recognized as a file and populated with an object.

Actual result

Field is populated as a string, resulting in the following error:

 ERROR #85909  GRAPHQL

Field "image" must not have a selection since type "String" has no subfields

File: src\templates\page.js:30:15

Environment

  System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
  Binaries:
    Yarn: 1.16.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.10.1-next.1 - C:\Program Files\nodejs\npm.CMD
  Languages:
    Python: 3.7.2 - /c/Users/r/AppData/Local/Programs/Python/Python37/python
  Browsers:
    Edge: 44.17763.1.0
  npmPackages:
    gatsby: ^2.13.6 => 2.13.6 
    gatsby-image: ^2.2.4 => 2.2.4 
    gatsby-plugin-manifest: ^2.2.1 => 2.2.1 
    gatsby-plugin-netlify-cms-paths: ^1.2.1 => 1.2.1 
    gatsby-plugin-offline: ^2.2.1 => 2.2.1 
    gatsby-plugin-react-helmet: ^3.1.0 => 3.1.0 
    gatsby-plugin-sharp: ^2.2.3 => 2.2.3 
    gatsby-source-filesystem: ^2.1.2 => 2.1.2 
    gatsby-transformer-remark: ^2.6.1 => 2.6.1 
    gatsby-transformer-sharp: ^2.2.1 => 2.2.1 

Umbrella issue to report Schema Customization API-related bugs: gatsbyjs/gatsby#12272

Release blog post about new API including potential breaking changes: https://www.gatsbyjs.org/blog/2019-03-18-releasing-new-schema-customization/

Thanks!

I ran into wanting to use this plugin for my MDX-based Gatsby pages and when quickly looking at the code it might be as simple as extending the node type check (focusing on frontmatter for now).

I'm happy to take a stab at a PR but wanted to check with your first for openness to such change and any issues you might already know about.

And cheers for your work so far!