Code Cleanup - Refactor autoComplete components to be more efficient, avoid duplicate id warnings in server logs #6360
Labels
Component: Code Infrastructure
formerly "Feature: Code Infrastructure"
Component: JSF
Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React.
Feature: Performance & Stability
Type: Bug
a defect
UX & UI: New React UI
Needs enough design work that it should probably go in the new React UI, not JSF
Searching the project, as part of the development for #5615, found that we have 13
p:autoComplete
components, of which 4 have the binding attribute (known bug ref Stack Overflow), and 2 of those are wrapped in p:fragment components (also, there are 3 other examples ofp:autoComplete
components wrapped inp:fragment
orp:outputPanel
components). So there are four variations to how the component is used, and we should review each, and get them all optimized and functioning properly to avoid these VERY server log heavy (#5749) duplicate id warnings.Example from server log of duplicate id warning from autoComplete component with binding attribute.
The text was updated successfully, but these errors were encountered: