You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The distinction between the two has proved somewhat artificial so I'm going to combine them.
The distinction originally was that "transformer" (or as known previously "parser") plugins were to sketch the outlines of the various data nodes but avoid expensive work leaving that for the typegen plugins. So for markdown, the remark parser would parse the frontmatter but not parse the markdown source as that's a lot more expensive leaving that for the typegen-remark plugin.
So while that performance tradeoff I still think makes a lot of sense, splitting the code into different modules doesn't as the two types of plugins are completely coupled and have to be installed together.
Which is confusing and unnecessary :-)
So let's eliminate it!
Should be mostly a bunch of pushing bits around so I should be able to get this done later.
The text was updated successfully, but these errors were encountered:
Some package renaming ( is deprecated as a concept/name — see gatsbyjs/gatsby#918) + lots of bug fixes + cache invalidation when plugins change.
Also potentially interesting for y'\''all in the future is Gatsby is now using Relay'\''s graphql compiler which lets you compose graphql queries together. So individual components can have a query and those get composed together on page components.
Closes expo/expo-docs#57
The distinction between the two has proved somewhat artificial so I'm going to combine them.
The distinction originally was that "transformer" (or as known previously "parser") plugins were to sketch the outlines of the various data nodes but avoid expensive work leaving that for the typegen plugins. So for markdown, the remark parser would parse the frontmatter but not parse the markdown source as that's a lot more expensive leaving that for the typegen-remark plugin.
So while that performance tradeoff I still think makes a lot of sense, splitting the code into different modules doesn't as the two types of plugins are completely coupled and have to be installed together.
Which is confusing and unnecessary :-)
So let's eliminate it!
Should be mostly a bunch of pushing bits around so I should be able to get this done later.
The text was updated successfully, but these errors were encountered: