ms-structural / ms-structural/femdesign-api
Refactor Motions.Rigid
Open
Nobody has claimed this yet.
framework:c#
priority:later
type:improvement
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Consider removing Motions.RigidPoint and Motions.RigidLine and use only Motions.Rigid.
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 locating the definitions and usages of Motions.RigidPoint, Motions.RigidLine, and Motions.Rigid in the API. Review how callers distinguish these types and identify the affected tests or examples. Done means the redundant types are removed and existing motion behavior continues to work through Motions.Rigid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100