Skip to content

JSF: avoid suggesting UIComponent default attributes on non-component tags - #9606

Open
NicolaIsotta wants to merge 1 commit into
apache:masterfrom
NicolaIsotta:taghandler-attrs
Open

JSF: avoid suggesting UIComponent default attributes on non-component tags#9606
NicolaIsotta wants to merge 1 commit into
apache:masterfrom
NicolaIsotta:taghandler-attrs

Conversation

@NicolaIsotta

Copy link
Copy Markdown
Contributor

TagImpl no longer inherits generic UIComponent attributes (like 'rendered') across all facelet tags. Introduce a ComponentTag wrapper so default component attributes are only provided for actual UI/composite components.

Add tests for the corrections, even if CI doesn't run them at the moment


^Add meaningful description above

Click to collapse/expand PR instructions

By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -

  • are all your own work, and you have the right to contribute them.
  • are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).

LLMs, Commit messages and PR description:

  • Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.
  • LLM assisted commits should be attributed with an Assisted-by: MODEL_NAME MODEL_VERSION line appended to the commit message.
    • Please mention coding assistance in the PR description too (eg. by adding the same Assisted-by line from above)
    • Please describe the changes in your own words - we'd like to know you understand the changes being made!

If you're a first time contributor, see the Contributing guidelines for more information.

If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.

PR approval and merge checklist:

  1. Was this PR correctly labeled, did the right tests run? When did they run?
  2. Is this PR squashed?
  3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
  4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)

… tags

TagImpl no longer inherits generic UIComponent attributes (like 'rendered')
across all facelet tags. Introduce a ComponentTag wrapper so default
component attributes are only provided for actual UI/composite components.

Add tests for the corrections, even if CI doesn't run them at the moment
@NicolaIsotta

Copy link
Copy Markdown
Contributor Author

To give a visual example, these are the attributes suggestions of f:ajax in NB 31:
image
While these are the suggestions with the PR applied:
image

For reference: https://jakarta.ee/specifications/faces/4.1/vdldoc/f/ajax

@mbien mbien added Java EE/Jakarta EE [ci] enable enterprise job ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) labels Sep 10, 2026
@apache apache locked and limited conversation to collaborators Sep 10, 2026
@apache apache unlocked this conversation Sep 10, 2026
@NicolaIsotta

Copy link
Copy Markdown
Contributor Author

BTW, I managed to make the web.jsf.editor unit tests work. Can I add another commit to this PR, or is it better to open a new one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) Java EE/Jakarta EE [ci] enable enterprise job

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants