"Save Map as..." behavior not intuitive

Open
  • Is something wrong?
#288 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
desktop

Research direction

Start by locating the “Save Map as...” command and tracing how it handles the current map and subsequent saves. The issue describes the expected behavior: after saving as map-2, later saves should update map-2 while leaving map-1 intact. Check the save flow and its tests, if present, to identify the change and confirm that behavior.

Written by the indexing model from the issue text.

Description

In most programs, when one uses the "Save As" function, it changes the currently "open" file so that subsequent saves will apply to the 'saved as' file.

For example, let's assume that someone is making a map called map-1. They are done with that part of that map, and want to save it as a different file. Let's call this file map-2, thus they press the Save Map as option and save their map as map-2. Let's say they make changes to the map, and save it again - these changes will not apply to map-2's file - no, they'll apply to map-1's file.

This current behavior is simply not what one would expect when using "Save As" - it's much closer to what some other programs (i.e. GIMP, among others) might call an "export as" rather than a "save as". I like using the Save Map as... so I can make a 'template' map, from which I can make new maps that conform to the same style. Me accidentally overwriting the template map multiple times has forced me to mark the file as read only to ensure I don't accidentally overwrite the file.

Dominant language
TypeScript
Stars
59
Forks
19
Avg merge
32m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from CCDirectLink/crosscode-map-editor

All issues in CCDirectLink/crosscode-map-editor

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.