export-world should export a full model system
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Scala
- Stars
- 20
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Calling export-world iteratively down the tree of child models is not difficult, but we will need to figure out some way of keeping track of, and dealing with exceptions relating to LevelSpace not being able to find the right .nlogo files. @qiemem do you have any suggestions?
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 at the export-world entry point and trace how it currently handles child models. Determine how LevelSpace should locate the right .nlogo files and how exceptions should be handled while exporting the full model system; done means iterative child-model export works without losing track of missing or incorrect files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100