Add removal of LegacyPropertyManagementTrait from MVC

[Hackwar]

User description

This is the documentation PR for joomla/joomla-cms#44907

---

PR Type

Documentation

---

Description

• Document removal of LegacyPropertyManagementTrait from MVC classes

• Add migration guide for deprecated set() and get() methods

• Provide code examples for property access changes

---

Changes walkthrough 📝

	Relevant files
Documentation	removed-backward-incompatibility.md Document MVC trait removal migration                                          migrations/54-60/removed-backward-incompatibility.md Add new section documenting LegacyPropertyManagementTrait removal Include migration examples from generic methods to direct property access Reference related PR #44907 for implementation details +15/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Incomplete Migration The migration guide doesn't address potential null property access issues when migrating from get() with default values to direct property access with null coalescing operator. Consider adding guidance for handling undefined properties. ```php // Old: $this->set('key', 'value'); $var = $this->get('key', 'defaultValue'); // New: $this->key = 'value'; $var = $this->key ?? 'defaultValue'; </details> </td></tr> </table>

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[HLeithner]

seems not to be done in 6.0