ms-structural / ms-structural/femdesign-api
Improve error handling for users
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Give user information about success/failed .fdscript
-
prompt messages from Pipe/log file
- https://github.com/strusoft/femdesign-api/issues/674#issuecomment-1451375360
Important error to catch are the one in log file and they are mostly due to incorrect fdscript.
i.e.
- https://github.com/strusoft/femdesign-api/issues/674#issuecomment-1451375360
-
Missing load case but the user try to run them
-
Missing load combination but the user try to run them
Several error can be spotted opening FEM-Design as it prompts you to what it is wrong.
i.e.
- Catch error when value are not in range (min value, maximum value)
- Catch error on input type (steel material on a concrete beam)
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 .fdscript execution and how messages are exposed through the Pipe/log file. Review the linked discussion for the intended prompt behavior. Done should include success and failure information, including missing load cases or combinations, out-of-range values, and incompatible input types.
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