Directly compare raw XML files in CI #6
Labels
Change: patch
[Issue / PR] describes a small non-breaking change, such as bugfix or an optimization
Domain: meta
[Issue / PR] describes change in the development process, documentation, maintenance etc.
good first issue
[Issue] can be addressed by a first-time contributor
Priority: medium
[Issue / PR] should be addressed without delay
Type: bug
[Issue / PR] addresses malfunction
Currently, to figure out whether the update is needed, there is a comparison between the currently published
data.json
file and adata.json
file that would be built out of the latest XML file:https://github.com/parzh/iso4217/blob/main/.github/workflows/publish-xml-updates.yml#L50-L58
Not only this introduces an unnecessary step of converting XML to JSON, but it also is prone to false positives in case if the potential new
data.json
file is in any way different (even if the change doesn't originate from the original data, – see #2):data.xml
;data.xml
with the XML content on maintainers' site;The text was updated successfully, but these errors were encountered: