microsoft / microsoft/AdaptiveCards
[iOS][Provide More Natural Dev Experiences for Swift Developers]
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
What platform is your feature request related to? (Delete other platforms).
- iOS
Describe the solution you'd like
The newer iOS developers are more familiar with Swift, so we need strategy on accommodating this need. Since objective-c library can be co-oped with Swift code base via bridge header, this may not be a big concern, but we need to have a better solution for custom renderers.
The custom renderer requires developers to interact with our c++ object model if values have to be read from json payload. This requirement may not be an issue to devs familiar with objective-c due to the language similarities and heritages, but it may be too burdensome to some swift developers.
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
No files or tests are named. Start by reviewing the iOS custom-renderer path, the Objective-C bridge-header integration, and how Swift currently reaches the C++ object model and JSON values. Done would require an agreed, concrete strategy for making custom renderers more natural for Swift developers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, ios, objective-c, swift
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100