NatLabRockies / NatLabRockies/REopt_API
Would be good to integrate two approaches to storing messages in database (Message and REoptjlMessageOutputs models), i.e. having just one model and handling messages from API and Julia consistently.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 125
- Forks
- 68
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 1
Description
This issue has no description.
Contributor guide
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
Compare the Message and REoptjlMessageOutputs models and trace how API and Julia messages are stored. Define the shared model behavior and verify that both message paths are handled consistently without duplicate storage models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100