Make use of TFM and OSSupportedPlatform to generate checks in targets of authored components
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 665
- Forks
- 134
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
Previously if someone referenced a component in an app that didn't meet the target / min versions, they were given an error. We should investigate achieving something similar by looking at the TFM and OSSupportedPlatform attribute and using that to add version checks in our generated targets which authored components include.
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 tracing how generated targets are produced for authored components and how TFM and the OSSupportedPlatform attribute are currently represented. Compare this with the existing incompatible-component error behavior; done means generated targets add equivalent version checks when an app's target or minimum versions do not meet the component requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100