ms-structural / ms-structural/femdesign-api
Create Custom Object to Group all the results
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
I do think that it is not necessary for the user to specify in which branch the result is stored.
I would propose to create the same workflow that it has been done for FdFeaModel.
My idea is to have a Single Object i.e. Results and get the values from it without the need of selecting the right type of Results.

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 inspecting the existing FdFeaModel workflow and how result types are currently selected. Determine the scope of a unified Results object and confirm how values should be accessed without branch-specific selection; done means the proposed grouping is implemented consistently and its behavior is covered by the project’s existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100