Outline structure of modularised jLEMS
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 11
- Avg merge
- 8h 6m
- Merged PRs (30d)
- 1
Description
Ideas for modularising jLEMS
These modules will make it easier to replace core implementations of jLEMS (e.g jLEMS or jLEMSDev) and abstract out the interaction with LEMS models by other Java applications.
API to model
Being worked on here:
Related to https://github.com/LEMS/jLEMS/issues/51
API to run time
Could be based on implementation of api here: https://github.com/LEMS/jLEMS/tree/development/src/main/java/org/lemsml/jlems/api
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 linked issue #51, the structure diagram, and the existing API under src/main/java/org/lemsml/jlems/api. Define and document the proposed modules and their API boundaries for model and runtime interaction. Done means the modularised structure is outlined and agreed for implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100