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

Skeleton [size] property is no longer a string accepting rem values but instead expects shapes #15535

Closed
LightBulbIdea opened this issue May 10, 2024 · 3 comments
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@LightBulbIdea
Copy link

Describe the bug

Skeleton [size] property is no longer a string accepting REM values. It now requires the developer to pass either 'circle', 'square' or undefined. This change appears to be a mistake since there's already a shape property in said component. Because of this new change we can no longer specify the size of the skeleton.

This changed was introduced on v17.16.1

v17.16.0 file:

@Input() size: string | undefined;

v.17.16.1 file: (This looks wrong)

@Input() size: 'circle' | 'square' | undefined;

Environment

Angular 17.3.4

PrimeNG 17.16.1

Reproducer

No response

Angular version

17.3.4

PrimeNG version

17.16.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20

Browser(s)

No response

Steps to reproduce the behavior

Code change to the skeleton's size property that seems unintentional.

Expected behavior

To be able to pass a size value rather than to be forced to pass in a shape since we already have a dedicated shape property.

@LightBulbIdea LightBulbIdea added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 10, 2024
@imaksp
Copy link

imaksp commented May 11, 2024

Hi, yes it looks like a mistake, introduced with this recent commit by @cetincakiroglu :
a521b10

@cetincakiroglu cetincakiroglu added this to the 17.16.2 milestone May 11, 2024
@cetincakiroglu
Copy link
Contributor

Hi,

Thanks for letting us know, we'll address it with the upcoming release.

F3KTOR added a commit to F3KTOR/primeng that referenced this issue May 11, 2024
cetincakiroglu added a commit that referenced this issue May 14, 2024
#15535 - skeleton value changed from a shape to string for rem values
@cetincakiroglu cetincakiroglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels May 14, 2024
@cetincakiroglu
Copy link
Contributor

Fixed in #15540

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

3 participants