I agree, but unfortunately Portal's edit forms for config items always apply settings into the production class (the XData block). Even worse, Portal ignores the source control status of the production class, so you can't prevent these changes. Portal users have to go elsewhere to add/edit System Defaults values. It's far from obvious, nor is it easy. And because they don't have to (i.e. the users can just make the edit in the Portal panel and save it) nobody does. We raised all this years ago, but so far it's remained unaddressed
Folder within VSCode? Or folder on your local disk, that you could browse using Windows Explorer or macOS Finder in order to see a set of textfiles containing classes, routines etc?
I've checked that it compile, is synchronized server-client and vice versa.
Is this referring to when you're using the Serenji extension? If so, understand that there is no client-side copy of your code (so no synchronization involved). Serenji works directly on your server-side code.
It's good. Only I'm missing the intellisense
Yes, Serenji doesn't yet do a good enough job of providing Intellisense. It's on our roadmap.
Did you intentionally start your Serenji service process on port 43221 rather than the default port, which is 43211?
You can check the status of that service process by running this command in a Cache Terminal:
D ^%Serenji
The output includes a section like this:
Serenji explore/edit/debug service
----------------------------------
Service status: Running
Primary port: xxx
Aux port min: xxx
Aux port max: xxx
Server address: xxx
Nice to see this preview appear, and being a Docker container made it easy for me to download, spin up and verify that our Serenji extension for VSCode seems to work fine. Not that I'm surprised, seeing how good at maintaining backward compatibility I've always found ISC to be.
Maybe the lack of line indent in Marc's post confused you. Try this:
Maybe this is what the OP is means by 'gitflow'
https://nvie.com/posts/a-successful-git-branching-model/
@Fred Gustafsson is this what you guys use?
Wanna see the current results before you vote? Just log out of DC. Then view the poll. When you're ready to cast your vote, log in again
I agree, but unfortunately Portal's edit forms for config items always apply settings into the production class (the XData block). Even worse, Portal ignores the source control status of the production class, so you can't prevent these changes. Portal users have to go elsewhere to add/edit System Defaults values. It's far from obvious, nor is it easy. And because they don't have to (i.e. the users can just make the edit in the Portal panel and save it) nobody does. We raised all this years ago, but so far it's remained unaddressed
See also https://community.intersystems.com/post/system-default-settings-versus-p...
Folder within VSCode? Or folder on your local disk, that you could browse using Windows Explorer or macOS Finder in order to see a set of textfiles containing classes, routines etc?
Please clarify what you are referring to when you say "client-side code".
Is this referring to when you're using the Serenji extension? If so, understand that there is no client-side copy of your code (so no synchronization involved). Serenji works directly on your server-side code.
Yes, Serenji doesn't yet do a good enough job of providing Intellisense. It's on our roadmap.
If you disable ObjectScript VSCode and enable Serenji I hope you'll be able to work the Serenji way. Please try it.
Did you intentionally start your Serenji service process on port 43221 rather than the default port, which is 43211?
You can check the status of that service process by running this command in a Cache Terminal:
D ^%Serenji
The output includes a section like this:
Nice to see this preview appear, and being a Docker container made it easy for me to download, spin up and verify that our Serenji extension for VSCode seems to work fine. Not that I'm surprised, seeing how good at maintaining backward compatibility I've always found ISC to be.