docs: record how the driver layer got here, and fix the docs it proved stale - #88
Open
priyanshujain wants to merge 6 commits into
Open
docs: record how the driver layer got here, and fix the docs it proved stale#88priyanshujain wants to merge 6 commits into
priyanshujain wants to merge 6 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
writing up how the driver layer got to its current shape turned up a pile of docs describing a system we deleted months ago. the in-app sdk went in april, the sidecar stopped serving ios in june, and coverage does not exist anywhere in the codebase at all.
new page at docs/development/driver-history.md: the timeline of what we tried, why each thing died, and the bugs that forced each move. commit shas and pr numbers throughout so anything on it can be checked.
the rest is bringing architecture.md, design-principles.md and four manual pages back in line with reality. also killed the system alerts claim, there is no alert handling in the proto or the sidecar or the driver interface.
one bit needs your eyes. the reason we deleted the in-app sdk is not recorded anywhere, pr #43 has no body, no comments, no linked issue. i wrote it up as the accessibility tree turning out to be enough, and said outright that is recollection and not record. change it if you remember it differently.
paper/system.md and paper/findings.md had the same uiautomator staleness. fixed those locally, they are not in this pr since paper/ is excluded.