ms-structural / ms-structural/femdesign-api

Create Custom Object to Group all the results

Open
#525 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

framework:grasshopper priority:unset type:proposal
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.

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.