-
-
Notifications
You must be signed in to change notification settings - Fork 15
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!: use newer angular framework version #754
Conversation
We are following the Conventional Commit Format. Please make sure that your Pull Request title and body conform to this format, otherwise, it might not be released. Here is a short example:
These are the most used types: (you can find more here)
In the Pull Request Body please describe what changes for the user of the application. If the user has to do things differently than before (excluding new functionality) please include |
We are following the Conventional Commit Format. Please make sure that your Pull Request title and body conform to this format, otherwise, it might not be released. Here is a short example:
These are the most used types: (you can find more here)
In the Pull Request Body please describe what changes for the user of the application. If the user has to do things differently than before (excluding new functionality) please include |
1 similar comment
We are following the Conventional Commit Format. Please make sure that your Pull Request title and body conform to this format, otherwise, it might not be released. Here is a short example:
These are the most used types: (you can find more here)
In the Pull Request Body please describe what changes for the user of the application. If the user has to do things differently than before (excluding new functionality) please include |
We are following the Conventional Commit Format. Please make sure that your Pull Request title and body conform to this format, otherwise, it might not be released. Here is a short example:
These are the most used types: (you can find more here)
In the Pull Request Body please describe what changes for the user of the application. If the user has to do things differently than before (excluding new functionality) please include |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #754 +/- ##
==========================================
- Coverage 55.72% 45.90% -9.83%
==========================================
Files 7 5 -2
Lines 192 183 -9
Branches 69 66 -3
==========================================
- Hits 107 84 -23
- Misses 56 94 +38
+ Partials 29 5 -24 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Restyled.io <commits@restyled.io>
// character (U+002C). Therefore, a COMMA character in a value MUST be | ||
// escaped with a BACKSLASH character (U+005C), even for properties that | ||
// don't allow multiple instances (for consistency). | ||
.replace(/,/g, ',') |
Check warning
Code scanning / CodeQL
Replacement of a substring with itself Medium
// escaped. On input, an escaped SEMICOLON character is never a field | ||
// separator. An unescaped SEMICOLON character may be a field | ||
// separator, depending on the property in which it appears. | ||
.replace(/;/g, ';') |
Check warning
Code scanning / CodeQL
Replacement of a substring with itself Medium
🎉 This PR is included in version 5.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Update angular framework
BREAKING CHANGE:
Might not be compatible with previous angular versions