Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Upgrade is hard and refactoring too big #119

Closed
jogelin opened this issue Nov 22, 2021 · 1 comment
Closed

Upgrade is hard and refactoring too big #119

jogelin opened this issue Nov 22, 2021 · 1 comment

Comments

@jogelin
Copy link

jogelin commented Nov 22, 2021

I am writing this issue to share about the upgrade from v1.7.5 to v3.

We are using this library since the beginning in our mono repo and we really liked the fact that we could make our forms typed.

We are trying to keep our repo up to date but with the last upgrade but we investigated what will be the cost of refactoring our forms and it is really too much.

In fact, being forced to create a new type with specific AbtractControl each time we have a complex object is impacting us too much.

And because the upgrade cannot be incremental, we decided to wait until Angular will make its own version. Th the imports will not be the same and we could upgrade step by step.

And now we would like to upgrade to Angular v13 but you don't propose a v1.x compatible version :(

What could we do? Removing simply your library?

@NetanelBasal
Copy link
Member

In fact, being forced to create a new type with specific AbtractControl each time we have a complex object is impacting us too much.

I'm not sure what you mean here.

@ngneat ngneat locked and limited conversation to collaborators Nov 22, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants