Audit log example shows unexpected behavior
- Dominant language
- Python
- Stars
- 58
- Forks
- 160
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 12
Description
I didn't carefully look at the log added in #1040 and now am noticing that it has a couple of unexpected things about it:
- location is tracked for a question event before the permissions are granted or the providers enabled
- location tracking is disabled but then location is provided for that event and the ones after it
See https://github.com/opendatakit/docs/blame/master/odk1-src/form-audit-log.rst#L134
@grzesiek2010 where did that log output come from? Is it actually behavior that Collect can produce?
Contributor guide
Research direction
Start with the example in odk1-src/form-audit-log.rst around line 134 and review the change from #1040. Determine whether the shown location events can be produced by Collect when permissions or providers are disabled; done means resolving the example's source and clarifying or correcting the documentation accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100