ms-structural / ms-structural/femdesign-api
SetEdgeConnection behaviour if Null is given
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Error handling in case of indexes or edge connection == null.
Suggestion:
if null, do not set any edge and skip to run the method
BUG:
Slab deconstruct return a surface where the order of the edge does not follow the order of the edge connection
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 SetEdgeConnection and the Slab deconstruct behavior described in the issue, then read the linked discussion for reproduction context. Verify how null indexes or edge connections and reordered edges are handled. Done means null inputs are skipped without an exception and the deconstructed surface preserves the expected edge-connection order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100