isc-kiyer
isc-kiyer
**Is your feature request related to a problem? Please describe.** I would like to have the ability to request swarm reviews directly from vs code (and add reviewers) rather than...
**Is your feature request related to a problem? Please describe.** I want to easily view the jobs attached to my changelist in the source control tab of VS code without...
There should be backward compatibility so we always first check for the existence of module.json and if not present, fall back to module.xml. With JSON would be good to have...
The package manager keeps a cache of available versions of modules locally for each repo. This is useful for more performant dependency resolution. However, at time of installing a module,...
Currently, many parts in IPM are using direct global references instead of macros. Which makes things hard to manage. For example, in %IPM.Extension.SourceControl.Perforce.Main, ^Sources(0,"FileTimeStamp",tName_".ZPM"), etc. We should change them to...
The module name should be updated to reflect the new name of InterSystems Package Manager. Also need to update any hardcoded references to the module name of zpm.
Currently, a few IPM macros are still using ZPM instead of IPM. For instance, in %IPM.Common.inc, #define ZPMHandledModules %ZPMHandledModules, etc. We should change them to be named with IPM. Also....
The package manager incorrectly throws errors on a semantic version like the following: 2.1.0-1m1 This had to be tweaked to 2.1.0-1.m1 for the package manager to consider it valid. However,...
If a package is already installed and needs to be upgraded, the package should be able to indicate upgrade steps to be run between any source and target versions. The...
Similar to other package managers (like npm/yarn), IPM should support a lock file (equivalent for Node JS apps is package.json vs package-lock.json). This will allow consumers to reliably reproduce dependencies....