ikonrad / gatsby-source-directus Goto Github PK

Hello,

first of all, thanks for writing this plugin!

But I have an issue:
Queried Items remain in cache.
When fetching data, the plugin shows the correct amount of items, but the ones that i deleted after last query remain in the results.
The only way I was able to delete those entries is deleting the .cache folder in the root

Any ideas?

I have a Directus database with some Markdown fields. I want to take this Directus Markdown data and display it in Gatsby as HTML.

All Gatsby Markdown blogs/tutorials I've seen talks about using gatsby-transformer-remark for compiling Markdown, but it assumes the Markdown is stored as .md files in the Gatsby folder structure.

Has anyone had success using GraphQL to compile Markdown data coming from Directus (or any other data source besides the file system)?

After installing and adding the plugin to my gatsby-config.js I get the following error:

error UNHANDLED EXCEPTION

  ReferenceError: regeneratorRuntime is not defined
  
  - fetch.js:39 
    /[gatsby-source-directus]/fetch.js:39:56
  
  - fetch.js:111 
    /[gatsby-source-directus]/fetch.js:111:10
  
  - fetch.js:145 Object.<anonymous>
    /[gatsby-source-directus]/fetch.js:145:2
  
  - v8-compile-cache.js:178 Module._compile
    /[v8-compile-cache]/v8-compile-cache.js:178:3    0
  
  - v8-compile-cache.js:159 require
    /[v8-compile-cache]/v8-compile-cache.js:159:2    0
  
  - gatsby-node.js:3 Object.<anonymous>
   /[gatsby-source-directus]/gatsby-node.js:3:14  
  - v8-compile-cache.js:178 Module._compile
    /[v8-compile-cache]/v8-compile-cache.js:178:3    0

Are you planning to update the plugin to Directus 7? I'm not a great developer and I'm learning React and Directus though from what I understand the new version of Directus doesn't use API keys anymore?

@iKonrad PR #4 was merged to fix issue #3, but there is no release that includes the fix to this.

Can you create a release so I can reference it in my package.json? (my project has a restriction that doesn't allow us to directly target commit hashes, otherwise I'd just target c7c97e0).

The plugin downloads all images to the Gatsby .cache folder, but all references to images from other database rows are broken. So if I have a "users" table that has a profile image for each row, I can't get a reference to that image to display on the user's profile.

I posted a question on Stackoverflow looking for help on the same thing. I'm also digging around this plugin's source code trying to solve the issue, but if anyone has any advice let me know.