licence + codefactor badges

[kelson42]

No description provided.

[kelson42]

@Jaifroid I wanted to add a badge for the CI on main too... but was not clear to me "what is actually the CI workflow?".

[Jaifroid]

@kelson42 Currently the CI workflow checks that a PR/push can successfully build the WASM versions. At the moment, it does this from scratch. When I've completed a PR on #12, it will do exactly the same, but by pulling libzim.a and dependencies from the appropriate openzim/release archive. This is a good check for this repo, I think. In an ideal world, we would add some testing, by automating the demo version, that the WASM is good for reading an archive and doing a search. But for now, it's probably a good enough test that the WASM and glue files can all be built successfully against the PR. Does that sound right?

[kelson42]

@kelson42 Currently the CI workflow checks that a PR/push can successfully build the WASM versions. At the moment, it does this from scratch. When I've completed a PR on #12, it will do exactly the same, but by pulling libzim.a and dependencies from the appropriate openzim/release archive. This is a good check for this repo, I think. In an ideal world, we would add some testing, by automating the demo version, that the WASM is good for reading an archive and doing a search. But for now, it's probably a good enough test that the WASM and glue files can all be built successfully agains the PR. Does that sound right?

Sounds perfect. Current CI is heavy because of the architectural choice. Once you won't compile all the dependencies anymore then we could run it on main at each push.... and put appropriate badge in README.md. That badge is important, at least to me, to quickly now if OK with current code base (and can be released for example).

[Jaifroid]

Apart from the pre-exisitng typo mentioned in comment, looks good to me.