mobile-dev-inc / mobile-dev-inc/maestro-docs
Update "Detecting Maestro in your app" docs to reflect port change
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 85
- Forks
- 92
- Avg merge
- 16h 6m
- Merged PRs (30d)
- 1
Description
The docs for Detect Maestro in your app state that iOS uses port 22087
This is no longer true in recent versions of maestro. By default, maestro uses port 7001 as discussed here
If this change was intended, could the docs please be updated to reflect it?
I'm opening an issue rather than a simple PR to change "22087" to "7001" because it seems the reality is more complicated and nuanced than that. As discussed here, the new sharding execution logic means maestro could be running on any port in the range of (7001..7128). Given that complication, it is not clear to me how the docs should be updated to account for this.
I'd be happy to open a PR with my best attempt at updating the docs to reflect the current situation. But I wanted to open this issue first because perhaps the maintainers have some context or understanding that I am lacking.
Please let me know if you'd like me to submit a PR for this change!
Or if there is some nuance or context you can share to clarify the situation, that would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
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 with the “Detect Maestro in your app” documentation page and read the linked discussion in issue 1816, especially the referenced comment. Clarify how the documentation should describe the default port and sharding range, then update the page once maintainers confirm the intended wording. Done means the page accurately reflects current Maestro behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100