Fix/backdrop disappearance #65
Merged
Conversation
This file contains 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
vqoph
force-pushed
the
fix/backdrop-disappearance
branch
from
5e15252
to
e787e09
Compare
|
cannot build du to : #66 |
added 2 commits
November 20, 2018 11:36
fix following error on npm install: Error, Unhandled rejection Error: Command failed: /usr/local/bin/git checkout error: pathspec '4.0' did not match any file(s) known to git. error on gulp version see olefredrik/FoundationPress#1316
vqoph
force-pushed
the
fix/backdrop-disappearance
branch
2 times, most recently
from
6a38e18
to
4ec2f5f
Compare
added 7 commits
November 20, 2018 11:54
commit from ng-snotify project artemsky/ng-snotify@a2174d7
vqoph
force-pushed
the
fix/backdrop-disappearance
branch
from
4ec2f5f
to
1e23b5d
Compare
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.
Hi, this is a fix proposal for the issue #57
The commit 6ceef59 is optional but can be useful
I've only reported the fix you done from the angular
Tell me if I have everything to do to make this PR relevant
Best regards