26
30
53
Addon to provide a locale switcher and react-intl for storybook
Events
Multi-paragraph text fields unable to query markdown
@mordonez I thought about it as well but decided against it because it means an additional library will be sent to the client and increases the load time.
Multi-paragraph text fields unable to query markdown
@matjack1 Thanks for the update.
I confirm that this functionality is not present anymore on our source plugin v5. If you really need it you can use the v4 of our plugin for now. The problem with using the v4 is that it can't be used with Gatsby 5 because the peer dependency only allows Gatbsy 4 as max version.
More news on this as soon as we decide where to go. Do you know when you know more about it?
Multi-paragraph text fields unable to query markdown
I've upgraded the datocms plugin to the v5 and I have the same problem with the childMarkdownRemark on the non existing field *Node. So this is actually a critical bug and should be fixed urgent as it is completely incompatibly with plugins like remark.
Jest globals differ from Node globals
@pkit right, but this.global doesn't have/need a jsdom property.
Jest globals differ from Node globals
@pkit unfortunately this doesn't work. What exactly should that do? this.global doesn't seem have the property jsdom.
Jest globals differ from Node globals
@pkit I'm using this for a server environment as well. But I have the same problems with the globals with JSDOM too. And there it's not that easy to create a custom environment and patch the globals.
Jest globals differ from Node globals
Does someone have a workaround for this problem?
And how can we support the project to get this fixed?
feat(gh-push): add fix/ as branch prefix
Add function and alias to delete a git branch with rebase as fallback
