Skip to content

Approx. 3 minute delay in seeing compiled local file changes in ObjectScript Explorer #33

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

Closed
swils024 opened this issue Mar 26, 2019 · 2 comments

Comments

@swils024
Copy link

This is similar to #19 but the emphasis is on the intended purpose of 'ObjectScript Explorer' and it's differences to 'Atelier Explorer' and 'Workspace' view in Caché Studio.

Why is it when you compile a .INT file using Ctrl + F7 in VSCode the change appears instantly in Caché Studio and a sync is triggered in Atelier/Eclipse but when you look at it in ObjectScript Explorer in VSCode there can be a significant delay before it retrieves the latest version from the server (almost as if it's not invalidating the cache to the retrieve the latest copy)? I don't think a notification is required but I do wish the ObjectScript Explorer was more trustworthy ie. the code I see here is what is currently on the server I'm pointing to.

Is the thinking behind the design that developers only need ObjectScript Explorer for exporting classes, routines etc to their workspace and that it shouldn't be used to compare local workspace / filesystem version with server version?

@daimor
Copy link
Member

daimor commented Mar 26, 2019

Server explorer shows the latest loaded version not direct from the server. And how it was designed my VSCode, not by me. When file saved, I call invalidation, but it may not work as I expected. Just need more time to check it, carefully.

And what the reason, to compare sources on server and local. The main idea when I added Explorer is to explore sources, which I don't have locally, such as System classes.

And even, when you open a file in explorer which you already have locally, it should open local version, not remote.

@swils024
Copy link
Author

@daimor Thanks for the feedback.

In VSCode, talking about 'Explorer' can be ambiguous/unclear because it could mean the 'file explorer' view as denoted by the 'two files' icon in or the 'ObjectScript Explorer' view denoted by the Intersystems logo. I agree that opening a file in the 'file explorer' view should be the file you have locally. This view doesn't know anything about the connection settings and simply reads a file from your file system. If I save and compile this file with some changes, I would expect to see these changes in the ObjectScript Explorer readonly view but the change doesn't appear to be immediate.

In a simple, single-user, stand-alone project scenario, comparing the server version with local version isn't really necessary after a compile as I can trust that when I receive a 'compile successful' notification that the changes that have been made locally to this file have been successfully transferred to the server - even if 'ObjectScript Explorer' view doesn't immediately reflect this .

@daimor daimor transferred this issue from daimor/vscode-objectscript-fork Jun 12, 2019
@daimor daimor closed this as completed Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants