The "MarkedForUpdate" property on %IPM.Storage.ResourceReference should have XMLPROJECTION = "NONE"

Open Beginner friendly
#1,248 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
tooling

Research direction

Start by locating %IPM.Storage.ResourceReference and its MarkedForUpdate property, then inspect how XML projection metadata is declared for nearby properties. Reproduce the package/publish and older-IPM installation steps from the issue; done means MarkedForUpdate is omitted from published module.xml while the module remains loadable in IPM 0.10.7.

Written by the indexing model from the issue text.

Description

bug

Describe the bug

The MarkedForUpdate property does not have XMLPROJECTION = "NONE", so it gets exported into a published module.xml and that package cannot be loaded using a <0.10.7 version of IPM

To Reproduce

Steps to reproduce the behavior:

  1. Create a test module or find one
  2. Mark a resource for update using the %IPM.Storage.ResourceReference:MarkResourceForUpdate() method
  3. Package/publish the module
  4. Try installing it with a <0.10.7 version of IPM

Expected behavior

Modules published in IPM 0.10.7+ should be able to be loaded using IPM <0.10.7

Dominant language
ObjectScript
Stars
41
Forks
29
Avg merge
3d 5h
Merged PRs (30d)
3

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/ipm

All issues in intersystems/ipm

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.