Improve now-sdk transform outcome

[aquarilis]

As it stands today, running the "now-sdk transform" command results in all xml artefacts being transformed into files named as follows:

[artefact_table_name]_[artefact_sys_id].now.ts

and which:

1. Are all dumped into a single "generated" folder without any particular sub-folder structure
2. Do not leverage Now.include statements to extract the code part from the rest of the object attribute

As such, the current "transform" method significantly limits the support of existing scoped applications, since that conversion doesn't offer a really usable set of code / files.

I wish the transform method could:

1. split the converted artefacts into more structured folder hierarchy:

• my personal preference would be by "target table", then by "object class" (a bit like what is shown when selecting "Configure > All" on a table or record in ServiceNow backend UI),
• but it could also be by "Server" vs. "Client" configuration pieces, then by object type, and finally by target table (or vice versa).
• Split by "target table" somewhere in the subfolder hierarchy (i.e. where the config object/script runs) would be a huge benefit to easily find something!
• option could be given in a command option ( --folder-hierarchy-type [ target_table_first | object_type_first ] something like that maybe?)

2. automatically extract script/HTML/XML field content into separate .js / .html / .xml files which are "Now.included" in the TS files, so as to make them ready to use

As far as I can see, we're not missing much to be able to go that the extra mile, are we?

[bryce-godfrey]

This is something we are working on for a near future release, a method of describing your desired taxonomy structure for generated content like this. Thanks for the input, we will consider some of this for how it will work.

[aquarilis]

thanks for your reply @bryce-godfrey! Much appreciated!

I know this SDK is not necessarily an open-source project or so, but I believe ServiceNow Partners who might be willing to shift development practices towards Fluent, they may be interested in having more visibility on the SDK roadmap, so as to know at which point it will be "mature" enough to support their regular development and consulting needs.

Is it something ServiceNow will be willing to share at some point or not at all?

(P.S: big up for release 4.0.0 and the ability to ship APIs more often 🍾, very much looking forward to that! 😉)