@David Hockenbroch 

Thanks!

I think the major assumption I forgot to mentioned was that this is an existing web app built on CSP that we would like to modernized with REST APIs.  

So to begin with the methods are defined in the CSP file and now we want to port them over to a REST API.  Since it's a generated class I get nervous calling it like I am but I don't see another way.

@Sergei Shutov Thank you!

How does one define this in an OpenAPI 2.0 spec?

@Brett Saviano 

Sorry, back again. Feeling like a dunce here . . . I updated my API using my OpenApi 2.0 JSON spec and the /api/mgmt POST call and looking in Studio, I can see my spec.cls is showing v 1.5 as I expect. When I refresh the explorer view (which is the live server, yes?) I'm still on v 1.4 which is my old spec.

Is there some other setting that might be preventing this refresh?

I looked here: Settings Reference - InterSystems ObjectScript for VS Code (intersystems-community.github.io), but I didn't find anything that stood out as a setting that would stop a refresh of the explorer view from showing updated classes on the server.

Whew.  That was it: the explorer view was hidden.

Thanks!

Thanks and agreed. It was on my locally installed IRIS on my own machine so I wasn't too worried, but yes, would never do that on a live server that others use or have access to.

Thank you, Brett.  I must still be missing something.

In the ObjectScript explorer, if I right click on the project I have an option to 'Export Project Contents'.  If I right click on any package or file, I only have three options: Remove from Project, Server Source Control and Server Command Menu.

I've skimmed the doc again but don't see anything obvious in terms of settings that I might be missing. 

Any ideas?

@Brett Saviano 

Thanks for your reply!  I am familiar with that doc but didn't reference it because we already set up for client side development.  Yes I could just edit the spec and impl classes on the server, but since our source control isn't hooked into the server, so I would still have the issue of getting the code generated and updated on the server (from /api/mgmt/) to my local repo.  

I tried the ObjScript Explorer to export, but it seems I can only export ALL the files.  That's not practical when I just want to export one package.  

However, using the Export Code From Server command does let me select individual classes so that's great! 

Question: if we scale up with use of OpenAPI 2.0, the use of /api/mgmt/ and stick with client side dev, how can we make source control more smooth?  In other words, is there a way to automatically export impl and spec classes to the client whenever they are updated?

Good to know about the disp class and makes sense.  One less thing to worry about.  

While I was playing around with this, a few times after compiling changes to the impl class, the disp class was then removed from the server (this was in Studio before I figured out to get them on the client).  Have you experienced this before and know what might cause that to happen?

Opening this back up because getting the classes to my local repo is proving to be challenging.

In VS Code I was able to open the code on the server, click 'Download' on the package and download it to my local repo.  Problem is that the only two classes that show up are impl and spec, but not disp.

In a similar vein, if I used the API to update the spec the updated code was now on the server (just as it first got there when I did the create using the API).  Now when I try to download the updated package to my local, well, it won't let me.  I have to download each file which isn't too cumbersome, but it's just one.  

How can I:

1) Get the disp class to get to my local so I can ship it to the remote repo and other servers

2) Make the update process using the API smoother

3) Bonus: create a web app programmatically so when my colleague starts to use it for his front end dev, he's ready to go.

Resolved by removed a lock on some global called ^oddProcess("default_project") or something like that.

How embarrassing for me.

Pro tip: check the names of your keys when you access them :)

Thanks all!

For some more context, I stopped trying to see what was going on by setting globals to debug.  I set the %response.TraceDump=1 so I can see the %session variable which is were I'm storing the value to the key of the object:

%session.Data("key")=array.%Get("key")

This is still no working as expected.  I even stepped through the code in the command line by calling the zLabel in the INT routine generated from the CSP and it worked as expected there.  

@Eduard Lebedyuk Thank you.  This IS true since I'm debugging a method defined on CSP page, I'm writing things to a global to check them on the terminal.  So that explains that.

How do you know that means that?

Thanks @Pravin Barton! This is helpful just to get a better send of how others use the framework.  We are still baby stepping into all of this and don't want to rush into implementing it as it's harder to untangle and "redo" once we're really rolling.  

Related to keeping your unit tests separate: so you don't export your unit test class files to a different ^UnitTestRoot?  Rather the ^UnitTestRoot is where the unit tests live in the cloned repository? 

@Timothy Leavitt thanks for the link to that post. I'm sure I've seen it before but more will make sense now that I have more experience with this.  

Related to the test coverage tool: do you have best practices or shortcuts as an individual developer?  Do you run the Test Coverage tool as your developing to see what lines of code are covered or not? We are thinking through how to arm the developer to write the most complete unit tests before sending to the remote and having Jenkins automatically rebuild everything and do the more extensive reporting.

Really appreciate the responses! 

@Dmitry Maslennikov This seemed to help as the changes to the HTML are instant with the changed setting, however the CSS didn't change.  After clearing the browser cache then I saw the changes.  Assuming there must be a browser setting that hold on to the CSS.  I'm not sure.  

We haven't quite solved this for our own app.  All the progress thusfar has been in the demo app from GitHub (the coffee shop).

Using the demo, the web folders are in the container.  I will try this though and see if it changes things.

After 30 mins or so both the CSS change (changed from Ariel to Times) and the HTML (added "TESTING!!!" in the heading) ended up refreshing.

Why is there this lag?  Must be the browser?

A update already: it seems the CSS has now updated on both browsers, but the HTML is still not updated.  This lag seems quite off.  When I update CSS locally (not Docker) it changes on refresh.  

@Guilherme Mendes Thank you.  That's exactly it.  That documentation was misleading, and I think it's fair to say so since there are so many ways to embed this and that into that and this!