Repository navigation
qml code need review #1672
Replies: 3 comments
|
Thanks for bringing this up! I'm not very familiar with QML myself, so input from people with Qt/QML experience would be especially valuable. Could you open an issue for QML support and reference our language support tracking issue, #470? We can link it as a sub-issue to help attract contributors with the relevant expertise. A few examples of the problems you'd like the review to catch would help define useful QML-specific rules. If you have experience with QML and would like to contribute those rules yourself, a PR would also be welcome! #470 outlines the contribution steps, and the new issue would be a good place to agree on the scope first. |
|
We should postpone language support PRs because the repository has a numerous language support PRs that are still open. |
|
I agree. As the QML codebase grows, the UI becomes harder to maintain and review without clear component boundaries, better structure, and consistent coding standards. Breaking the UI into smaller reusable components and improving review guidelines would make it much easier to manage. |
Uh oh!
There was an error while loading. Please reload this page.
The UI is written in QML with Qt, and the codebase is still quite large. This makes the UI code harder to maintain and review
All reactions