bazelbuild / bazelbuild/rules_apple
Make `bazel run` always use a shared simulator?
- Dominant language
- Starlark
- Stars
- 593
- Forks
- 334
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 9
Description
Currently there is this logic https://github.com/bazelbuild/rules_apple/blob/261d19ed7c057364bf5d04a8df400fed8ad40b9b/apple/internal/templates/ios_sim.template.py#L504-L510 but the flags used to determine the temporary path are also used to set a specific version for a test runner so you don't have to have a custom test runner rule. I wonder if we should just always use a persistent path here, maybe unless the user requests a temporary simulator specifically.
Contributor guide
Research direction
Start with apple/internal/templates/ios_sim.template.py around lines 504-510 and inspect how the flags select the simulator path and test-runner version. Determine whether persistent use should be the default or whether an explicit temporary-simulator option is needed; the issue is done when the intended behavior is specified and implemented with corresponding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100