fix: move leapwallet CSS library import to component-specific usage #281
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
…uction environments
chore(deploy-web): update Google Analytics configuration
chore(deploy-web): update Google Analytics configuration
Move leapwallet CSS library import to component-specific usage
|
Good find, thanks for fixing. |
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.
Description
The import of the Leap Wallet CSS library was previously located at the top level of the component, which inadvertently affected the container class on the main console website. This container class is crucial for maintaining the layout and ensuring that the div elements do not extend beyond a specified width.
Changes Made
Moved the import of the Leap Wallet CSS library from the top of the component file to the component-specific context.
This change addresses layout issues by isolating the CSS impact to only where it is needed, preventing unintended interference with the container class and preserving the intended design constraints.
Benefits
Screenshots
Before
After