chore: drop unused ocs/providers.php #54370
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This appears to have been originally intended to support the providers list functionality mentioned in the OCS <=v1.7 spec. That is, appears to be an implementation of what was suggested be made available at `https://domain.tld/ocs/providers.xml`. However best as I can tell it never worked. It also doesn't appear in the v2.0 spec drafts. Signed-off-by: Josh <[email protected]>
joshtrichards
added
3. to review
skjnldsv
approved these changes
Aug 12, 2025
come-nc
approved these changes
Aug 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This appears to have been originally intended to support the provider file functionality mentioned in the OCS <=v1.7 spec. That is, appears to be an implementation of what was suggested be made available at
https://domain.tld/ocs/providers.xml.However best as I can tell it never worked (there is no viable route or code path to reach it).
It also doesn't appear in the v2.0 spec drafts.
TODO
Checklist