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.

Sign up for GitHub

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

Jump to bottom

fix(umi-build-dev): hashHistory don't work if it's configured in plugin #568

Merged
merged 1 commit into from
May 30, 2018
Merged

fix(umi-build-dev): hashHistory don't work if it's configured in plugin #568

merged 1 commit into from
May 30, 2018

Conversation

sorrycc
Copy link
Member

@sorrycc sorrycc commented May 30, 2018

No description provided.

@coveralls
Copy link

coveralls commented May 30, 2018 •
edited
Loading

Pull Request Test Coverage Report for Build 535

  • 0 of 4 (0.0%) changed or added relevant lines in 1 file are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.005%) to 21.345%
Changes Missing Coverage Covered Lines Changed/Added Lines %
packages/umi-build-dev/src/plugins/hash-history.js 0 4 0.0%
Files with Coverage Reduction New Missed Lines %
packages/umi-build-dev/src/plugins/hash-history.js 2 0.0%
Totals Coverage Status
Change from base Build 533: -0.005%
Covered Lines: 509
Relevant Lines: 2598
💛 - Coveralls

@sorrycc sorrycc merged commit ee41ad7 into master May 30, 2018
@sorrycc sorrycc deleted the fix/hash-history branch May 30, 2018 08:11
sorrycc pushed a commit that referenced this pull request Jun 23, 2022
@devilmancbc @sorrycc
feat: add doc for lint (#568)
9f7217b
xierenyuan pushed a commit to xierenyuan/umi that referenced this pull request Jun 23, 2022
@devilmancbc
feat: add doc for lint (umijs#568)
aec3fbe
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
type(bug)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@sorrycc @coveralls