-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Removing PrimeNG components from Angular modules #2537
Comments
mehmet-erim
added a commit
that referenced
this issue
Jan 3, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 3, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 6, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 6, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 6, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 7, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 7, 2020
…tive and add abp table instance #2537
mehmet-erim
added a commit
that referenced
this issue
Jan 7, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 7, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 7, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 8, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 8, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 9, 2020
mehmet-erim
added a commit
that referenced
this issue
Jan 9, 2020
thediaval
added a commit
that referenced
this issue
Jan 9, 2020
thediaval
added a commit
that referenced
this issue
Jan 9, 2020
thediaval
added a commit
that referenced
this issue
Jan 9, 2020
thediaval
added a commit
that referenced
this issue
Jan 9, 2020
thediaval
added a commit
that referenced
this issue
Jan 9, 2020
thediaval
added a commit
that referenced
this issue
Jan 10, 2020
thediaval
added a commit
that referenced
this issue
Jan 10, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We decided to eliminate all PrimeNG imports and declarations from Angular modules. Because the new version of PrimeNG has a lot of breaking changes.
The development we will make related to this issue won't cause any breaking changes. You will be able to continue using PrimeNG,
ConfirmationService
andToasterService
as like before.Three components will be developed:
The text was updated successfully, but these errors were encountered: