Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix for the Link issue #15

Merged
merged 1 commit into from
Mar 17, 2019
Merged

fix for the Link issue #15

merged 1 commit into from
Mar 17, 2019

Conversation

kalwalt
Copy link
Owner

@kalwalt kalwalt commented Mar 17, 2019

See issue: #6 and #7
I solve the issue #6 adding a "/" at the start of the path of every Link component, in this way gatsby is assured of internal link..
Instead for issue #7 i added the gatsby-transformer-javascript-frontmatter and in the blog (/en/ and /it/) index page i added:

export const frontmatter = {
  id:  '02',
  title: "pagina blog",
}

in thys way that page has not an empty id anymore.

…ded frontmatter id to .js files with frontmatter plugin
@kalwalt kalwalt added the bug Something isn't working label Mar 17, 2019
@kalwalt kalwalt self-assigned this Mar 17, 2019
@kalwalt kalwalt added this to In progress in Template Development Mar 17, 2019
@kalwalt
Copy link
Owner Author

kalwalt commented Mar 17, 2019

I think i can merge it, issue #8 was related and it will not happens (i hope).

@kalwalt kalwalt merged commit 13d5458 into dev Mar 17, 2019
Template Development automation moved this from In progress to Done Mar 17, 2019
@kalwalt kalwalt deleted the fixes-link-component branch March 25, 2019 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

1 participant