Add layout option for list field documentation

[marcorensch]

User description

Added missing layout parameter – specifically mentioned the option for fancy select.

---

PR Type

Documentation

---

Description

• Added layout parameter documentation for list field

• Documented fancy select layout option for dynamic lists

---

Diagram Walkthrough

flowchart LR
  A["List Field Documentation"] -- "Add layout parameter" --> B["layout optional parameter"]
  B -- "supports" --> C["joomla.form.field.list-fancy-select"]

Loading

File Walkthrough

	Relevant files
Documentation	list.md Add layout parameter documentation                                              docs/general-concepts/forms-fields/standard-fields/list.md Added documentation for the layout optional parameter Explained usage of joomla.form.field.list-fancy-select for dynamic list layouts Clarified that layout can be customized or use predefined fancy select option +1/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Not Applicable: This PR only updates documentation and does not introduce or modify application code that performs critical actions or logging, so audit trail compliance cannot be assessed from the diff. Referred Code - **layout** (optional) use define custom layout or use `joomla.form.field.list-fancy-select` as layout to get a more dynamic layout for your lists. - **required** (optional) if set to true, the first field option should be empty, see last example. Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Documentation Only: The changes are documentation text; no identifiers or code naming are added or modified, so naming compliance cannot be evaluated from this diff. Referred Code - **layout** (optional) use define custom layout or use `joomla.form.field.list-fancy-select` as layout to get a more dynamic layout for your lists. - **required** (optional) if set to true, the first field option should be empty, see last example. Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No Runtime Code: The PR modifies documentation only and does not add executable logic where error handling or edge cases would apply, so compliance cannot be assessed here. Referred Code - **layout** (optional) use define custom layout or use `joomla.form.field.list-fancy-select` as layout to get a more dynamic layout for your lists. - **required** (optional) if set to true, the first field option should be empty, see last example. Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Documentation Only: No user-facing error messaging logic is introduced in this documentation change, so secure error handling cannot be evaluated from the diff. Referred Code - **layout** (optional) use define custom layout or use `joomla.form.field.list-fancy-select` as layout to get a more dynamic layout for your lists. - **required** (optional) if set to true, the first field option should be empty, see last example. Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: No Input Handling: The change documents a layout option but adds no executable input handling or data processing code, so validation and security handling cannot be assessed from the diff. Referred Code - **layout** (optional) use define custom layout or use `joomla.form.field.list-fancy-select` as layout to get a more dynamic layout for your lists. - **required** (optional) if set to true, the first field option should be empty, see last example. Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Improve documentation clarity and grammar Rephrase the description for the layout parameter to correct a grammatical error and enhance clarity. docs/general-concepts/forms-fields/standard-fields/list.md [14] -use define custom layout or use `joomla.form.field.list-fancy-select` as layout to get a more dynamic layout for your lists. +Defines a custom layout for the field. Use `joomla.form.field.list-fancy-select` for a more dynamic list layout. [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 4 __ Why: The suggestion corrects a grammatical error ("use define") in the documentation, which improves clarity and readability for developers using this feature.	Low
More

[HLeithner]

Thanks for you contribution, I'm not 100% convinced on the form of adding this as "special" attribute to the list field only but since the whole section could be improved I will merge this for now.

I would also like to ask you if you like to improve the https://manual.joomla.org/docs/next/general-concepts/forms-fields/standard-form-field-attributes/ section? Adding all generic supported attributes to this (also the 1to1 mapped html attributes).

In this case the layout attribute could be described more in detail.

anyway thanks for the contribution.