MerginMaps / MerginMaps/qgis-plugin
Feature Request: Warn about project directory upload/publish behavior
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 20
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
Description
I just now attempted to upload a few hundred GBs to Mergin since I didn't make my project in a blank/empty sub-directory, but rather the root of my temp/scratch drive.
I know this is my fault since I was lazy and didn't make a clean working directory, but I wasn't expecting Mergin to pull every file on the same path level, regardless of whether or not they're referenced by the project.
Maybe some text could warn users about this behavior, since it is expected as per @saberraz.
Thanks!
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
The issue names no file, test, or entry point. Trace the project upload/publish flow and identify where users can be warned that files at the project directory level may all be included. Done means the behavior is clearly communicated before upload or publish, with appropriate coverage for the warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100