This repository has been archived by the owner on Mar 27, 2023. It is now read-only.
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.
Overview
4.4.4
golden/clr-angular.d.ts
@cds/core
&@cds/angular
("^5.6.0"
) used into sub packages to latest version - to resolve some warnings when building.build:icons:zip
build:icons:zip
from build steps - zip files no longer part of @clr/icons@typescript-eslint/eslint-plugin
&@typescript-eslint/parser
)This PR includes work based on collaboration with @bbogdanov and @Jinnie
How to test it
To test the dev app:
To test website
Testing packages
Setup testing tools
Release packages
locally
Check package information and dependencies
Use the new package to create new application
$ npx @angular/cli@13 new demo-app $ cd demo-app $ npx @angular/cli@13 add @clr/angular@13.0.0-next --registry http://localhost:4873 $ npm run start
Performance
Known issues
When building, there is a warning that if I'm not wrong, it is already fixed, but it seems not backported. Need investigation.
When creating new application with
ng new
and trying to compile the application this error could be foundThe workaround at the moment is editing
button.base.d.ts
and changingariaDisabled
to not includenull
as type.Release
After this PR is merged this package/s could be publish under
next
tag to NPM asv13-angular.next
orv13.next
(tag name still underconsideration)