Better logic for editing mapped items

Open
#1,006 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
git
Domain
backend, devtools

Research direction

Start by reviewing related issue #997 and tracing the existing Embedded Git and IPM source-control decision path. Done means unmapped items use the current namespace rules, mapped development packages use the owning namespace's settings, and mapped non-development packages cannot be edited.

Written by the indexing model from the issue text.

Description

Related to #997, but a more general requirement for Embedded Git with IPM.

  • If an item is not mapped, follow source control rules for current namespace (top level or IPM-based)
  • If an item is mapped, and the IPM package containing it exists in the namespace default routine database for some other namespace and was loaded in dev mode, edits should follow that other namespace's source control settings
  • If an item is mapped and in a non-dev mode IPM package, don't allow it to be touched.
Dominant language
ObjectScript
Stars
22
Forks
14
Avg merge
1d 9h
Merged PRs (30d)
5

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.

More from intersystems/git-source-control

All issues in intersystems/git-source-control

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.