ms-structural / ms-structural/femdesign-api
Error Handling
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
LogFile stores helpful information that might provide some insight in case of errors.
Same happen with Pipe.
We should consider to read those output and raise some warning/error if necessary.
i.e. Large Deformation has been detected (pipe)
i.e. Database file has been created with an higher version of the program (logfile)
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 locating the LogFile and Pipe handling mentioned in the issue, then inspect how their output is currently exposed. Define which output conditions should produce warnings or errors, including large deformation and a database file created by a newer program version. Done means those conditions are detected and reported consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100