[FEATURE REQUEST] Check security enforced value globally.
Open
Nobody has claimed this yet.
Estimation - 3 (M)
Feature request
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Currently, we check the value of lock_enforced configured in setup.xml in each activity where we want to check its value and act accordingly.
I think we should avoid this redundant check and code it in some activity or fragment just to do the check once or have the check called every time the user navigates between activities or fragments.
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 tracing how lock_enforced is read from setup.xml and checked across the relevant activities and fragments. Identify a shared entry point that can handle the value during navigation, then define a test plan showing that the check is no longer duplicated and still applies wherever required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100