search

arnoudkooi / sn-scriptsync

Use sn-scriptsync in combination with SN Utils to be able to code in VS Code, including all benefits of a full fledged code editor
https://marketplace.visualstudio.com/items?itemName=arnoudkooicom.sn-scriptsync
Other
43 stars 28 forks source link

Error saving files #2

Closed dtJon closed 5 years ago

dtJon commented 5 years ago

I have followed the example of your video and created a set of files for a widget. The Scriptsync tab is up and shows [1]. I hit the purple icon in the widget editor and the files all get created. However, if I try to save a file I get the following error.

The instance name is in the path twice. Any idea what could be causing this?

{ "errno": -2, "code": "ENOENT", "syscall": "open", "path": "/Users/jonlind/Documents/sn-scriptsync/instancename/instancename/settings.json" }

Thanks again--I am so excited by this and can't wait to make it an integral part of my workflow.

arnoudkooi commented 5 years ago

Could you check if you have opened /Documents/sn-scriptsync/ in ServiceNow as folder? Maybe you opened /Documents/sn-scriptsync/instancename/ What is the OS you use?

Maybe we cans schedule something to go over.

arnoudkooi commented 5 years ago

Do you need help on this, or can I close it?

dtJon commented 5 years ago

I am so sorry--I figured it out. I was in the wrong folder. I thought I hadn't submitted this in the first place. My apologies. Please close it.

On Mon, Jan 7, 2019 at 12:42 PM arnoudkooi notifications@github.com wrote:

Do you need help on this, or can I close it?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/arnoudkooi/sn-scriptsync/issues/2#issuecomment-452057062, or mute the thread https://github.com/notifications/unsubscribe-auth/AAg7wJ5V_t_HGQF4owQwvw-96IWAzUPzks5vA6M6gaJpZM4Zlldf .

arnoudkooi commented 5 years ago

no, problem, glad it works.

dtJon commented 5 years ago

I'm working on getting Babel wired up so that I can use ES2016 and output ES5 compatible code. Right now I'm thinking I'll create a version of the files with an "ES2016.js" or "ES2017.js" extension, wire up VSCode to run babel transforms on save of those, and then overwrite the originals that your tool outputs. That should automatically sync back up, I think.

The big issue, though, is that I need a place to save the > ES5 code so you can continue to work on it. Maybe a table in ServiceNow with a document ID/field name referencing the ES code?

Does this seem like a bad idea?

Thanks for your kick ass tool. It's changed my life. Jon Lind