Icon Row CMS Component #2305
Merged
Icon Row CMS Component #2305
Conversation
This file contains hidden or 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
|
Testing passed |
A-Wheeto
reviewed
Mar 3, 2025
| Components::Blocks::EnrolmentSplitCourseCard, | ||
| Components::Blocks::TextWithAsides | ||
| Components::Blocks::TextWithAsides, | ||
| Components::Blocks::IconRow |
Contributor
There was a problem hiding this comment.
As we are adding a new component to this list, it would be nice to order them alphabetically for tidiness.
A-Wheeto
approved these changes
Mar 3, 2025
Contributor
A-Wheeto
left a comment
A-Wheeto
left a comment
There was a problem hiding this comment.
One minor comment, but LGTM
Fixing a few issues in the icon_block system
msquance-stem
force-pushed
the
2961-icon-row-strapi-component
branch
from
11f673b to
84dcd40
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.
Status
Review progress:
What's changed?
Steps to perform after deploying to production
If the production environment requires any extra work after this PR has been deployed detail it here. This could be running a Rake task, migrating a DB table, or upgrading a Gem. That kind of thing.