ms-structural / ms-structural/femdesign-api
Load Group does not follow other components logic
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Input
The following input should use the "value list" technique
- LoadCaseRelationship
- Type
Others
- LoadCaseRelationship is missing "simultaneous"
- Add documentation
- change order Favourable with Unfavourable to match FEM-Design GUI.
- implement "custom" if possible
Simplifying
-
LoadCategoryDatabase.Default can directly output a list of Load Category. Same behaviour as MaterialDatabase
-
LoadCategoryDatabase.ListLoadCategoryNames can be removed. override to string for load category class will display the name
-
LoadCategory.GetLoadCategoryByName should be LoadCategory.GetCategoryByName|Index
-
remove not necessary components
-
error handling in case of Temporary load group https://strusoft.freshdesk.com/a/tickets/39279?note=47373722451
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 tracing the LoadGroup components named in the issue, then compare LoadCategoryDatabase with MaterialDatabase. Review the LoadCaseRelationship and Type items, the LoadCategoryDatabase and LoadCategory entry points, and the temporary load group error-handling requirement. Done means the checklist items are resolved, documented, and consistent with the FEM-Design GUI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100