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

Documentation: Migration guide to PrimeNG v18 doesn't include "InputTextarea" to "Textarea" #17425

Open
2 of 4 tasks
peach-v33 opened this issue Jan 17, 2025 · 1 comment
Open
2 of 4 tasks
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@peach-v33
Copy link

Describe the bug

The version 18 migration guide does not include that "InputTextarea" and "InputTextareaModule" are no longer available, and were replaced by "Textarea" and "TextareaModule". Probably should be in the "Removed Components" section with a note that Textarea can be used instead, but the old version is removed not deprecated.

Version 17: https://v17.primeng.org/inputtextarea

Version 18 (and 19): https://v18.primeng.org/textarea (https://primeng.org/textarea)

Pull Request Link

No response

Reason for not contributing a PR

  • Lack of time
  • Unsure how to implement the fix/feature
  • Difficulty understanding the codebase
  • Other

Other Reason

On the clock at work. Would have to contribute in my personal time (may do that in future, but for now, logging the bug).

Reproducer

not relevant. It's documentation.

Environment

Issue is on the documentation on the main primeng site, not my environment.

Angular version

19.1.1

PrimeNG version

v19

Node version

20.18.0

Browser(s)

Chrome.

Steps to reproduce the behavior

  1. Go to the v18 Migration guide: https://primeng.org/guides/migration
  2. Look at the list of deprecated and removed components. InputTextarea isn't there.

Expected behavior

InputTextarea should be mentioned with appropriate instructions for migrating to Textarea.

@peach-v33 peach-v33 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 17, 2025
@can-oezkan
Copy link
Contributor

can-oezkan commented Jan 17, 2025

It should also be noted that the directive pInputTextarea is renamed to pTextarea.

Unfortunately angular is not throwing an error when pInputTextarea is used. So you have to do a global search and replace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants