Fixed the invalid type error while running init with a numeric folder name#45
Merged
yoshinorin merged 1 commit intohexojs:masterfrom Nov 29, 2018
Conversation
1 similar comment
yoshinorin
approved these changes
Nov 29, 2018
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
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 PR fixes an invalid type error that occurs while running
hexo initwith a numeric folder name.E.g. Executing
hexo init 233will produce the error as follows:Since there'll be a need to create a new hexo project with numeric folder name in some cases, I've ensured that a string will be passed to the
resolve()function.