maproulette / maproulette/maproulette-frontend

Deleted virtual project prevents creation of new project with the same name

Open
#1,213 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
JavaScript
Stars
167
Forks
39
Avg merge
16h 34m
Merged PRs (30d)
11

Description

Hi,

This was my first time to try to create a MapRoulette challenge. As I was unfamiliar with the interface and options, I initially create a Project with the "Virtual" setting, assuming I would be able to add new challenges to that as well.

Turns out you can only add existing challenges to a virtual project, not new ones. That by itself is not an issue (although I would recommend to document this more clearly on the options tooltip), but when I subsequently deleted the virtual project, and attempted to create a new project with exactly the same name, I received the error below about a unique constraint being violated.

Clearly, deleting the project does not remove the reference to it in some table, causing this issue. I guess this may be a safeguard for virtual projects referencing the same project name. However, when there are no references, as in my case with an entirely new unused project, it should be possible to definitively delete a project.

afbeelding

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Reproduce the sequence of creating a virtual project, deleting it, and creating another project with the same name, then trace the project deletion path and the unique-constraint error. Done means an unused deleted project no longer prevents reuse of its name, with coverage for this sequence.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.