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($theme-default): front matter prev / next links #1140

Closed
wants to merge 1 commit into from

Conversation

sullivanpt
Copy link

fixes bug introduced with #1068.

Summary

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Docs
  • Build-related changes
  • Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

  • Chrome
  • Firefox
  • Safari
  • Edge
  • IE

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature
  • Related documents have been updated
  • Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

Fixes bug in 1.0.0-alpha.30 where adding this front matter to top of page causes build to fail (assuming using default theme and the file /tutorial/README.md exists

---
next: ./tutorial/
---

@sullivanpt sullivanpt mentioned this pull request Dec 29, 2018
15 tasks
@@ -53,7 +53,18 @@ export function isActive (route, path) {
return routePath === pagePath
}

function normalizedPagesMap (pages) {
return pages.reduce((map, page) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some thoughts i had while looking at this: Compute the map only once and update in dev mode when the site data changes. Some check like here and then recompute the map might work.

module.hot.accept(VUEPRESS_TEMP_PATH + '/internal/siteData.js', () => {

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems a very good idea, but webpack hot module replacement is way outside my skill set. I guess I should add learning it to my 2019 new year's resolutions! Also, where do I save the page map, the site object seems like it's not currently passed in.

@ulivz ulivz closed this in b24c317 Jan 15, 2019
@sullivanpt
Copy link
Author

Thanks for incorporating a fix/revert in alpha.32. confirm my build issue is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants