This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 974
Move navigation logic into new component #8189
Labels
Milestone
Comments
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Apr 10, 2017
Resovles brave#8189 Auditor: @bridiver
4 tasks
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Apr 10, 2017
Resovles brave#8189 Auditor: @bridiver
4 tasks
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Apr 11, 2017
Resovles brave#8189 Auditor: @bridiver
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Apr 11, 2017
Resovles brave#8189 Auditor: @bridiver
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Apr 12, 2017
Resovles brave#8189 Auditor: @bridiver
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Apr 12, 2017
Resovles brave#8189 Auditor: @bridiver
closed via 1cdaaf3 |
This was referenced May 23, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Test plan
#8205 (comment)
Describe the issue you encountered:
Move logic related to top navigation out of
main.js
file into new component. This way it will be ready for redux component patternThe text was updated successfully, but these errors were encountered: