@available attribute on function mocked incorrectly
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 886
- Forks
- 102
- Avg merge
- 6h 36m
- Merged PRs (30d)
- 2
Description
when a protocol is marked with a @available(*, deprecated... on a function, mockolo specifies the entire type as @available(*, deprecated, ... instead of just the function
is that expected behavior and desirable at Uber? or simply an oversight
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 reproducing the protocol case described in the issue, with a deprecated @available attribute on one function, and inspect the mockolo-generated output. Compare the generated availability annotation on the type with the annotation on the function; done means the behavior is clarified and the generated mock applies the attribute at the intended scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- testing, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100