[Bug]: Declarative settings are always rendered last #47109
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
When using declarative settings, the settings are always rendered last.
But if you specify a priority higher than a "legacy" setting, it should be rendered before them.
Steps to reproduce
- Add a declarative settings on a existing section
- set higher priority than other
- see the setting is always rendered last
Expected behavior
Should have the same control over the priority as with legacy settings.
Installation method
None
Nextcloud Server version
master
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
DeclarativeManager::getFormIDs only returns the IDs sorted, but not the priority so we can not sort in the settings app.