1.0 #852
Closed
1.0 #852
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Lerna conversion * hapi->express * new plugin system (and several plugins) * filesystem->graphql schema compilation
Now supports * eq * ne * in * regex * glob Also made start at supporting ability to query distinct list of values in a field. Also got Jest going and added tests for the basic queries + all the query operators.
Fixes "distict" for arrays.
Old method wasn't pulling out unique fields from subobjects e.g. frontmatter on Markdown.
This in the future can be further refined e.g. resize images, add retina versions, etc.
Fields in one type can create links by ending any field with ___TYPE_NAME e.g. from Markdown frontmatter you can link to a file like There may or may not be a better way to do this. Running with this for now. ```yaml --- title: My cool post backgroundImage___File: ./my-cool-image.jpg --- ```
It'll need updated when building for sites not at root.
Before typegen plugins had to map between AST types and GraphQL types. The idea was there could be "abstract" AST types (like Markdown) from which multiple GraphQL types could be created e.g. different markdown renderes e.g. Remark and Markdown-it. This extra abstraction proved to be more complicated than it's worth. It'll probably be very uncommon to want to have multiple output graphql types. Removing this abstraction makes typegen plugins simpler as now every AST type has a GraphQL type created and plugins just need to extend types they care about with their fields. Creating custom graphql types or fields can be as simple as modifying the AST to add/compute some extra data (if this is cheap — expensive computation and user driven computation should be reserved for custom graphql fields)
* Add a note on windows installation * Add missing dependencies into gatsby-plugin-typescript doc * Make HTMLPath configurable * Fix dev-cli readme * Use redux to managed program.extensions * Slashify all paths * Fix relativePath and clean no-used var * Get program.extensions from redux * Add a rootPath config * Some refactors * Run yarn format * Deal with config.rootPath for default layout * Fix bad rebase * Fix documention style * Add typescript definition for gatsby-link * Remove superfluous typescript example * Add vscode config to execute prettier on save More info: https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode * Imprive joi validation on rootPath * Remove useless tsconfig.json * Remove unused var * Use program from redux * Improve rootPath config (default config and regex validator) * Ensure schema is created even if the project hasn't got any source plugin Fix #811 * Find a webpack config that deals with all env \o/ This configuration works with basics configuration and with a custom `rootPath` (even with a typescript stack) It was tested with build and develop commands * Move default config into redux * Take english version to vscode/settings comment * Add some unit-test for `rootPath` * Make `src` as default rootPath * Rename `intermediate-representation` to `cache` * Add `public` into webpack root entries * Ignore .cache folders * Refactor `www` project with the new file directory * Refactor gatsbygram project with the new file directory
* Refactor data layer * new node schema w/ "content digest" required instead of ad hoc "hash" key * New cache module for typegen plugins to cache their data * Save and restore node data state * rename 'parser' plugins to 'transformer' * Update tests + add basic tests for gatsby-transformer-json * Add simple tests for yaml transformation * Add a test for transformer-sharp * Rename function * Add test for transformer-remark * Build and copy over built src to websites when building them so they're truely running from HEAD * Require the HTML component from the new src directory * Make imports relative + remove gatsby-helpers * Move fonts from the static directory to the src directory since we import with webpack * Correct path
* Pretty json output (easier to debug) * Don't include contentDigest into node.id It's cause duplication on content update * Deal with contestDisgest changes
* Updates to gatsby-dev-cli README * Document commands
* Fix id generation for JSON/YAML nodes + more tests * Debugging * Remove debug * Disable devtools when building
* Add the plugin creating the action to the action to ease debugging * Fix bugs in adding page dependencies plus only add if new * Upgrade Prettier to 1.2.1 and re-run format * Up sites to latest canary * Move route writer to own module and only write when pages change * Add new custom bound action creator which filters out unneeded actions * Split the query-runner module into 5 modules with clearer responsibilities * Remove requires to now missing file * Address feedback * Update dependencies
* Try to speed up lerna bootstrap * Lerna uses 'exec' now instead if 'run'
* Update to contentDigest * Wait for all queries to finish * Actually save new connection dependencies * This was leftover code which started causing trouble with caching
…g package scripts (#836) * Update to contentDigest * Wait for all queries to finish * Actually save new connection dependencies * This was leftover code which started causing trouble with caching * revert, run still used for executing package scripts
* Add `test:watch` command * Add ts-loader as dependency * Refactor typescript-plugin to be style compliant * Update README.md with tsconfig.json
Most people aren't going to use this so don't ship it to everyone. Also, more pressing, the remotedev server spits out a big error on startup right now which is very confusing.
|
Deploy preview ready! Built with commit 84b2c91 |
|
Deploy preview ready! Built with commit 84b2c91 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.