Open bobbyg603 opened 2 years ago
@jodaka can you please merge this change? We would like to deprecate our fork. Thanks!
I wish I could! I'm just a casual user of angular-tree-component and would love to see this PR merged. No idea why I had enough rights to review/approve your PR but I certainly don't have rights to merge it.
I wish I could! I'm just a casual user of angular-tree-component and would love to see this PR merged. No idea why I had enough rights to review/approve your PR but I certainly don't have rights to merge it.
ha! dang you could've fooled me š. really disappointing to see libraries get abandoned by their maintainers.
I wish I could! I'm just a casual user of angular-tree-component and would love to see this PR merged. No idea why I had enough rights to review/approve your PR but I certainly don't have rights to merge it.
ha! dang you could've fooled me š. really disappointing to see libraries get abandoned by their maintainers.
@bobbyg603 , @jodaka have you a forked version of the lib yet with the Angular 13+ supported?
@ikruglik yes, our forked version that targets Angular 13 can be found on npm
npm i @bugsplat/angular-tree-component
hi @tobiasengelhardt, I've updated this project to use Angular 18. It's been 3 years since the last commit, perhaps you might let us take over the project?
@bobbyg603 I wish I could, but I have no rights to merge, push or change anything in this project.
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?
Closes #915
What is the new behavior?
Adds support for Angular 13 and builds library as 'partial' Ivy
Does this PR introduce a breaking change?
Other information
BREAKING CHANGE: Library is now built with 'partial' Ivy