Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the support for BPL and DTL files #60

Open
evshvarov opened this issue Oct 31, 2019 · 12 comments
Open

Add the support for BPL and DTL files #60

evshvarov opened this issue Oct 31, 2019 · 12 comments
Labels

Comments

@evshvarov
Copy link
Member

BPL stands for Business Process, DTL - for Data transformation rules.
Both are classes which have GUI editors in IRIS.

@daimor daimor added the enhancement New feature or request label Nov 26, 2019
@jtsalten
Copy link

This is mandatory if we want VS Code to be a real alternative to Studio... even to Atelier... as the modern ID for IRIS.

@daimor
Copy link
Member

daimor commented Jan 19, 2020

Jose, I'm not against this feature, if InterSystems (or any other company) would pay for it, I will do it faster ))

@cristianojs
Copy link

Daimor,

Maybe can put these features in a Enterprise Version? What you think about that?

@daimor
Copy link
Member

daimor commented Feb 21, 2020

Cristiano, we thought about to add such staff like support for Ensemble and DeepSee as an Enterprise extension of this extension. Would your company be ready to pay for it, as monthly/yearly subscription, or maybe just pay for development?

@daimor daimor self-assigned this Apr 17, 2020
@mvhenderson
Copy link
Contributor

mvhenderson commented Apr 23, 2020

The management portal already has UI for both BPL and DTL and support server side source control as well as other things like lookup tables and default settings. Wondering if a stripped down "BTL, DTL, etc" source control hook could be used for this at least as an interim - it doesn't touch cls, rtn, etc and simply writes to the same working copy.

@daimor
Copy link
Member

daimor commented Apr 23, 2020

When used SourceControl Class, I think no problem. The main reason for adding such support to the extension is to make it work with SCM inside VSCode. At the moment, it is possible now without UI only, just as classes.

@mvhenderson
Copy link
Contributor

is to make it work with SCM inside VSCode

Right - I'm saying until there is full support via this extension they could use a stripped down source control hook that writes DTL/BPL changes to the same working copy folder as VS code.

@isc-bsaviano
Copy link
Contributor

This extension will support embedding the new Angular versions of the graphical editors (BPL, DTL, Rule) when they are implemented. It will not support the legacy Zen editors. Support for the Angular Rule Editor will be added by #1014. The server-side code required for VS Code support will be released in version 2023.1 so you can start using that integration shortly!

@evshvarov
Copy link
Member Author

evshvarov commented Mar 20, 2023 via email

@isc-bsaviano
Copy link
Contributor

Yes, the GUI edits will handle server-side source control. VS Code will update the local copy of the file when changes are saved so the editors can be used for client-side workflows as well.

@evshvarov
Copy link
Member Author

evshvarov commented Mar 20, 2023 via email

@isc-bsaviano
Copy link
Contributor

The modern Angular does support server-side source control. There have been a few bugs in that functionality fixed for 2023.1 so maybe you are experiencing one of them. The next 2023.1 preview will contain the VS Code integration and source control bug fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants