fix: #1468 client standalone ui update #1560
Merged
+359
−28
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
duong-se
reviewed
Jun 4, 2020
packages/marketplace/src/components/ui/client-app-detail/client-app-header.tsx
Outdated
Show resolved
Hide resolved
duong-se
reviewed
Jun 4, 2020
packages/marketplace/src/components/ui/client-app-detail/client-app-header.tsx
Outdated
Show resolved
Hide resolved
nphivu414
approved these changes
Jun 4, 2020
vuhuucuong
force-pushed
the
fix/1468-client-standalone-ui-update
branch
from
cbc3f04 to
85d2539
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.
Pull request checklist
Does this close any currently open issues?
fixes: #1468
Please check if your PR fulfills the following requirements:
yarn build) was run locally and any changes were pushedyarn lint) has passed locally and any fixes were made for failuresyarn test) has passed locally and any fixes were made for failuresPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: #1468
What is the new behavior?
On mobile:
On desktop:
Does this introduce a breaking change?
Other information
Include some css layout bug fixes