chore(demo): fix Customization.Dialogs page
#969
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
nsbarsukov
requested review from
MarsiBarsi,
vladimirpotekhin and
waterplea
as code owners
nsbarsukov
force-pushed
the
dialogs-customization-demo-page
branch
from
a53e0b5 to
2727a14
Compare
|
Visit the preview URL for this PR (updated for commit 2727a14): https://taiga-ui--pr969-dialogs-customizatio-kjcd9ila.web.app (expires Tue, 09 Nov 2021 09:09:15 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 |
|
@waterplea @vladimirpotekhin @splincode review, please |
splincode
approved these changes
Nov 9, 2021
waterplea
approved these changes
Nov 9, 2021
|
|
vladimirpotekhin
pushed a commit
that referenced
this pull request
Nov 10, 2021
splincode
pushed a commit
that referenced
this pull request
Nov 15, 2021
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Closes #967 (comment)
What is the new behavior?
Does this PR introduce a breaking change?