ms-structural / ms-structural/femdesign-api
Result points component and result reader
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Should we also add result points while we create labelled sections? Or are result points unnecessary if we implement labelled sections?
Originally posted by @xRadne in https://github.com/strusoft/femdesign-api/issues/554#issuecomment-1300731378
https://strusoft.fogbugz.com/f/cases/117287
Create GH component to define, evaluate and read result points:
- Constructor for result point
- Result reader for result point
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 reviewing the existing result-point constructor and the surrounding result-point component work described in issue #583. Trace how result data is currently evaluated and read, then implement the missing result reader and verify that result points can be read as well as defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100