Fixing #68 #74
Merged
Fixing #68 #74
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
kalwalt
added
bug
kalwalt
commented
Apr 12, 2019
| @@ -55,7 +55,7 @@ BlogIndexPage.propTypes = { | |||
| } | |||
|
|
|||
| export const pageQuery = graphql` | |||
| query BlogIndex | |||
| query BlogIndex($id: String!) | |||
There was a problem hiding this comment.
This cause the issue: we receive the wrong id frontmatter for this reason!
See also below...
kalwalt
commented
Apr 12, 2019
| @@ -76,7 +76,7 @@ export const pageQuery = graphql` | |||
| } | |||
| } | |||
| } | |||
| markdownRemark | |||
| markdownRemark(id: { eq: $id }) | |||
There was a problem hiding this comment.
...linked to the comment above.
|
Well done, this can be merged! |
This was referenced Apr 12, 2019
Merged
Merged
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.
This fix issue #68 as said in the issue the problems happens only for th blog index page. The problem came because a wrong GraphQL query. See more in the comment below.