You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[x] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
We're in the process of upgrade from Angular 12 to 14, and are also upgrading our dependencies to the latest versions. We were using v4 of content loader, and bumped to v7. We're seeing build failures due to the use of the "height" and "width" inputs, which after investigating the code, were removed in v6. This breaking change was not documented, nor is an alternative suggested, so we will need to figure out how to maintain the expected behaviour without the benefit of documentation.
Expected behavior
Breaking changes to component inputs are documented and alternatives are potentially suggested, where reasonable.
Minimal reproduction of the problem with instructions
Use the <content-loader> component and attempt to set [height] and/or [width] inputs.
What is the motivation / use case for changing the behavior?
An undocumented breaking change makes for a poor developer experience when upgrading libraries.
Environment
Angular version: 14.2.0
Browser: N/A
For Tooling issues:
- Node version: 16.16.0
- Platform: Linux
Others:
This is an Nx environment, fwiw, but that generally has no effect on
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
We're in the process of upgrade from Angular 12 to 14, and are also upgrading our dependencies to the latest versions. We were using v4 of content loader, and bumped to v7. We're seeing build failures due to the use of the "height" and "width" inputs, which after investigating the code, were removed in v6. This breaking change was not documented, nor is an alternative suggested, so we will need to figure out how to maintain the expected behaviour without the benefit of documentation.
Expected behavior
Breaking changes to component inputs are documented and alternatives are potentially suggested, where reasonable.
Minimal reproduction of the problem with instructions
Use the
<content-loader>
component and attempt to set[height]
and/or[width]
inputs.What is the motivation / use case for changing the behavior?
An undocumented breaking change makes for a poor developer experience when upgrading libraries.
Environment
The text was updated successfully, but these errors were encountered: