[FEATURE REQUEST] Make brandable document provider enforce visibility
Open
Nobody has claimed this yet.
Estimation - 3 (M)
Feature request
Settings
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
After https://github.com/owncloud/android/issues/3379, the option to show or hide the could be enforced via setup.xml or MDM
New parameter call document_provider_visibility or similar, with false as default. That means, document provider with no visibility.
It will be independent from locking methods.
TASKS
- Research (if needed)
- Create branch feature/feature_name
- Development tasks
- Implement whatever
- ...
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/feature_name into master
PR
- App
- Library (if needed)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #3379 and the existing setup.xml or MDM configuration handling for the document provider. Define how a document_provider_visibility setting should be read and verify that its false default hides the provider independently of locking methods; the issue does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100