Skip to content
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

Maintaining the next version of this package #36

Open
iwantwin opened this issue Feb 10, 2022 · 4 comments
Open

Maintaining the next version of this package #36

iwantwin opened this issue Feb 10, 2022 · 4 comments

Comments

@iwantwin
Copy link

iwantwin commented Feb 10, 2022

Hey @riccardomariani ,

as discussed I've created a follow-up package that we will maintain to be up to date for the latest angular versions.

Github project: https://github.com/ebenefits/odata-v4-ng
Docs url: https://ebenefits.github.io/odata-v4-ng/

Npmjs package: https://www.npmjs.com/package/@ebenefitsbv/odata-v4-ng
To install: npm install --save @ebenefitsbv/odata-v4-ng

This new package will only be compatible for angular > 13., for anything below 13 your old package works fine :)

We kept your name around as the original author. You can see all the changes we made to it compared to the latest version of your package here: ebenefits/odata-v4-ng@v1.3.4...v13.0.0 If you see anything you don't like, feel free to tell me.

If you would like you can update the readme to warn users that this package is no longer in development. We've linked to your package for use in angular version below 13. Also in the changelog we've linked to your repository for older versions.

We will do our best to maintain this new package, keep it up to date, and also fix any issues that might arise.
Of course feel free to contribute to the package if you feel like doing so later ;)

@riccardomariani
Copy link
Owner

Hi @iwantwin,
thank you so much for your will to keep the project alive.
I appreciate it!

@riccardomariani
Copy link
Owner

Hi @iwantwin ,
I Made the changes to the README to warn users of the project.
Let me know if it looks good and if I can help with something.
Thank you.

@iwantwin
Copy link
Author

Looks good, hopefully we can help everyone :)

If you want to you could mark your library deprecated on npm as well and redirect users to our new package. It might trigger people and help them update to the new version. If you don't want to that's fine of course :)

@riccardomariani
Copy link
Owner

I marked the npm package as deprecated and updated the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants