syntax highlighting incompatibility

[michal-kapala]

Currently syntax highlighting breaks highlighting for other file types, this is likely a problem with scope names.

As a workaround you can simply disable the extension when working with other file types and enable it when needed.

[mbienvenu]

Hi Michal.... does this extension work with Jitterbit's Cloud Studio? Wondering if we can use this extension to track changes to do Github actions with the Cloud Studio code changes.

[michal-kapala]

@mbienvenu the extension provides language support for Jitterbit scripts which are the same for Design Studio and Cloud Studio.

It does not interact with Jitterbit API or its internal version control system (being honest im not even sure if it is git-based, should be). I don't know of an equivalent to GitHub Actions available for Jitterbit deployment events, or if integration with JB deployments is possible at all. Maybe it can be achieved using Connector SDK, however Jitterbit scripts themselves dont offer any reflection mechanisms or real file system access.

If you aim to create an independent GitHub mirror, that should be doable. Here are the steps I would take:

1. Export your Cloud Studio project as Jitterpack file, save and decompress it (Jitterpacks are just regular .zip archives)
2. Use jitterbit-extractor to extract raw scripts and recover the virtual file hierarchy
3. Init a git repo from the extracted project directory, commit and push your code so you can use GitHub Actions

You'd need to repeat the process (or automate it) for every deployment you want tracked. From there you can use VSCode's in-built Git source control or any other tool for change tracking. This extension doesn't interact with Git in any way.