Remove solutions tsconfig

[alan-agius4]

Following the issues highlighted in https://docs.google.com/document/d/1eB6cGCG_2ircfS5GzpDC9dBgikeYYcMxghVH5sDESHw/edit?usp=sharing and discussions held with the TypeScript team. Together with the TypeScript team it was decided that the best course of action is to rollback this feature.

In future, it is not excluded that solution style tsconfigs are re-introduced.

Closes #18040, closes #18130 and closes #18170

[LayZeeDK]

Isn't this considered a breaking change? In which version will this land?

[alan-agius4]

@LayZeeDK, why is this a breaking change? We’ll be running migrations to revert back the changes from existing projects.

It’s scheduled to land in 10.1

[LayZeeDK]

1. Do you consider introducing solution-style configs a breaking change?
2. Do automated migrations negate breaking changes?

[alan-agius4]

Do you consider introducing solution-style configs a breaking change?

No, solutions style tsconfig only effects the IDE’s. it’s not used by any compilation.

Do automated migrations negate breaking changes?

Certainly not.

[mhosman]

When you are gonna release this fix??

[alan-agius4]

This will be available in 10.1.0.

Today we’ll be releasing the pre-release version and you can try it out using ng update @angular/cli -—next

[LayZeeDK]

Do you consider introducing solution-style configs a breaking change?

No, solutions style tsconfig only effects the IDE’s. it’s not used by any compilation.

Fair point.

Do automated migrations negate breaking changes?

Certainly not.

Thanks, that's also my impression.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}