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

refactor: make the prepare process clearer and modify the resolve alias #277

Merged
merged 3 commits into from
May 3, 2018

Conversation

meteorlxy
Copy link
Member

@meteorlxy meteorlxy commented Apr 27, 2018

  • Write notfound route to the temp route file instead of adding in app.js
  • Make the resolveOptions process in prepare clearer
  • Change the @theme alias to theme directory. Add @themeLayout and @themeNotFound aliases for Layout.vue and NotFound.vue respectively.

@meteorlxy
Copy link
Member Author

@yyx990803 @ulivz

Review wanted~~~

@ulivz
Copy link
Member

ulivz commented Apr 28, 2018

@meteorlxy Code change looks good, but I need to take some time to run your code at my side, please wait for some time.

@meteorlxy
Copy link
Member Author

@ulivz Hope to be merged ASAP~ I want to fix some issue or add some features based on this PR.

const outDir = siteConfig.dest
? path.resolve(siteConfig.dest)
: path.resolve(sourceDir, '.vuepress/dist')

// resolve theme
Copy link
Member

Choose a reason for hiding this comment

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

move this section down? There are currently two // resolve theme blocks.

@yyx990803
Copy link
Member

LGTM after the small change requested.

@meteorlxy
Copy link
Member Author

@yyx990803 Tweaked, sir!

Copy link
Member

@ulivz ulivz left a comment

Choose a reason for hiding this comment

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

@yyx990803 I will merge this change and continue to develop for plugin API (#240).

@meteorlxy Thanks for the great work, and this change is very good, but before plugin API is stable, I hope we can avoid refactoring code on a large scale. or there will be many conflicts, thank you.

@meteorlxy
Copy link
Member Author

@ulivz I know that, and I'm willing to help consider about the plugin API together.

Another refactor PR #314 has nothing to do with the core, and I think it's good for maintainability.

@ulivz
Copy link
Member

ulivz commented May 1, 2018

@meteorlxy Do you use slack or telegram? I can create a channel for that.

@meteorlxy
Copy link
Member Author

meteorlxy commented May 1, 2018

Oh, I didn't use them before, but I can try them. Which one do you prefer?

(How about Wechat first, LOL)

@meteorlxy
Copy link
Member Author

@ulivz I tried slack, and my email is meteorlxy.cn@gmail.com

@ulivz
Copy link
Member

ulivz commented May 3, 2018

@meteorlxy I have invited you to vuepress.slack.com.

@ycmjason
Copy link
Contributor

ycmjason commented May 3, 2018

@ulivz sorry but I just saw this. Any chance I could join the slack or is this selected personell only? 😂😂😂 Wouldn't mind at all if not possible. 😁

@ulivz
Copy link
Member

ulivz commented May 3, 2018

@ycmjason sure, can you provide the email?Let me invite you.

@ycmjason
Copy link
Contributor

ycmjason commented May 3, 2018

@ulivz me@ycmjason.com
Wohoo! 🎉

@ulivz ulivz merged commit fd547ea into vuejs:master May 3, 2018
@meteorlxy meteorlxy deleted the patch-2 branch May 3, 2018 13:17
@hmatalonga
Copy link
Contributor

@ulivz

Could I also join the vuepress slack? It doesn't hurt to try asking 😂

I would like to follow along the Plugin API plans and future discussions...

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.

5 participants