Open
Conversation
Co-authored-by: Armando Pérez Marqués <gmandx@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Adding more parameters to the page context will allow having more flexibility when creating page graphql queries. Right now the parameters allowed are either the ones that Gatsby adds to the context by default (like path), or the ones added statically through the globalContext.
Adding a callback to be able to map entry properties to Gatsby's page context object, allows for more flexibility when creating graphql queries, being able to query specific data based on the entry properties.
using this map:
we are now able to use the locale parameter in the page graphql query.