Support saving files to the server
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 65
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
I believe that this will also require user accounts and permissioning (since many people seem hesitant about making their work-in-progress models available to the public). Or maybe the initial draft of this should just upload all files into one central pool...?
We should also think about restrictions for what can and can't be uploaded. We don't really want people uploading any old thing they feel like putting on the server. What should the size limit be? Do we need to check that the file is a valid '.nlogo' file? Should we verify that the model passes the compiler before accepting it? (Probably not.)
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
Start by reviewing issue #189 and the eight-comment discussion, focusing on the unresolved choices around accounts, permissions, upload restrictions, size limits, and .nlogo validation. No implementation files or tests are named, so identify the server entry points and existing account or file-handling paths before work begins. Done requires an agreed design and an implemented, tested server-side save flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript
- Domain
- authentication, authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100