v0.3.1

Generalized script-step parsing

Before

Prior to this release, the tool skipped parsing script steps that weren't marked as "supported" and printed only the script-step name and a warning to the sanitised script text file (the text files that look the same as the script in the FileMaker script workspace).

Example: Aus URL einfügen ⚠️⚠️⚠️ FM-XML-EXPORT-EXPLODER: UNKNOWN SCRIPT-STEP [ ID: "160" ] ⚠️⚠️⚠️

After

Starting with this release, the fm-xml-export-exploder parses each script step with a generalized script-step-parser and try to read each parameter. Not all parameters can be parsed yet, but unsupported ones will be marked in the sanitized script output.

Example: Aus URL einfügen [ SSL-Zertifikate verifizieren: OFF ; Auswahl: ON ; Mit Dialog: OFF ; Target: $$my.result ; ⚠️ PARAMETER "URL" NOT PARSED ⚠️ ; $curloptions ]

As you can see, the already supported parameters are now present, instead of hiding them all and just adding a warning for the hole script step as before. This change also means that we now support many more steps than before, and can more easily add support for the missing ones. You can follow the progress of supported script-steps here: #28

What's Changed

• feat: parse commit transaction by @bc-m in #37
• feat: parse open transaction by @bc-m in #38
• feat: parse revert transaction by @bc-m in #39
• feat: parse set error logging by @bc-m in #40
• feat: parse insert current date/time by @bc-m in #41
• feat: merge parse commit with generic parser by @bc-m in #42
• feat: parse all steps with generic parser by @bc-m in #43

Full Changelog: v0.2.1...v0.3.1