-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(module:icon): change tag of nz-icon from <i> to <span> #7586
Conversation
This preview will be available after the AzureCI is passed. |
Codecov Report
@@ Coverage Diff @@
## 14.0.x #7586 +/- ##
=======================================
Coverage 92.09% 92.10%
=======================================
Files 502 502
Lines 16739 16747 +8
Branches 2625 2629 +4
=======================================
+ Hits 15416 15424 +8
+ Misses 1056 1055 -1
- Partials 267 268 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@simplejason Thanks for bugfix and etc. |
* chore: update to v14 chore: update chore: update chore: update to v14 * chore: fix monaco css styles errors * chore: add optionalChainNotNullable to skip errors due to angular bug * chore: update schematics with v14 * chore: update routing to fix errors of ngx-hover-preload * feat(module:icon): change tag of nz-icon from <i> to <span> (#7586) * feat(module:icon): change i tag to span * feat(module:icon): fix some styles after icon changed * feat(module:icon): do not update v9 * feat(module:icon): fix tests Co-authored-by: simplejason <simplejason.coder@gmail.com> * fix(module:icon): add missing nz-icon attribute * chore: update schematics with project name * chore: update package.json of components * chore: fix wrong tag name Co-authored-by: hullis <wendellhu95@gmail.com>
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?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information