modelix / modelix/modelix.core
Use ModelQL in the advanced model client/server
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 16
- Forks
- 10
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 26
Description
One reason for performance issues is that nodes are loaded lazily while traversing the model. The purpose of the ModelQL is to load all the required data before working with it. This is also useful for the advanced model client/server.
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 reading the advanced model client/server and the existing ModelQL implementation to understand how model data is currently loaded while traversing. The work is done when the client/server uses ModelQL to load all required data before processing, with performance behavior verified against the issue's lazy-loading concern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100