fititnt / hxltm-action

[non-production-ready] Multilingual Terminology in Humanitarian Language Exchange. TBX, TMX, XLIFF, UTX, XML, CSV, Excel XLSX, Google Sheets, (...)

Home Page:https://hxltm.etica.ai/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

hxltm-extras-action: ad hoc GitHub Actions for non-HXL / non-HXLTM cli tools

fititnt opened this issue · comments

Both for convert to new formats that HXLTM reference tooling may never do directly (that would make it too heavy on dependencies) and because there is some data preprocessing for tabular data before even start to think to HXLate (so, hxltmcli don't work, because it needs at least input be HXLated; the hxltmdexml was special case because input is XML mapped on the ontologia, so never would exist such special tooling) makes sense to at least tell everyone (even if is just for our internal use) which tools to use to pre-process or post-process.

Then, there is one problem. We're using GitHub actions for HXL / HXLTM, but most tools that do have cli tools to manipulate data don't have any published version on GitHub Market place, including very popular cli tools to deal with CSV or tabular data.

The plan

While this issue here is not about this repository, is at least a reference place to mention which strategies we use to create such GitHub actions, so even at least we can get things going.

"One big with everything" or several smaller actions?

I'm not sure which approach to follow, but one "One big with everything" is anti-pattern. But it may works to know which tools we decide to create separate action.

Also, one advantage of get the approach of simple abstract the command line tools, is that is is easier to create several of these actions and they still works on long term. So, the point here is for example allow the #5 be implementable without make too much hacks.