ms-structural / ms-structural/femdesign-api
PointSupport constructors and static methods using implicit conversion
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
It is not obvious to the user using the hint that they can use a Point3d in the following static method:
Is there a way to specify this? This problem applies for more constructors and static methods than this specific example.
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 by reading FemDesign.Core/Supports/PointSupport.cs around lines 167-178 and identify how the referenced constructors and static methods expose implicit Point3d conversions. Investigate whether the API can make those accepted conversions visible in usage hints, then determine how the same approach would cover the other affected constructors and static methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100