Support for XML/HTML tags on the API calls and a myriad of other things #20
Commits on Oct 1, 2021
Commits on Oct 6, 2021
Commits on Mar 12, 2022
-
🐛 Fix default config directory permission to 0755
To avoid "permission denied"
Commits on Mar 15, 2022
-
Merge pull request Omochice#9 from nikukyugamer/fix/initial-created-c…
…onfig-dir_permission 🐛 Fix default config directory permission to 0755
Commits on Oct 14, 2023
-
Add renovate.json (Omochice#11)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
-
-
Update module github.com/mattn/go-isatty to v0.0.19 (Omochice#12)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
-
fix(deps): update module github.com/urfave/cli/v2 to v2.25.7 (Omochic…
…e#13) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Commits on Oct 15, 2023
-
chore(deps): update actions/checkout action to v4 (Omochice#16)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
-
chore(deps): update actions/setup-go action to v4 (Omochice#17)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
-
chore(deps): update goreleaser/goreleaser-action action to v5 (Omochi…
…ce#18) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Commits on Oct 17, 2023
-
-
fix(deps): update module github.com/mattn/go-isatty to v0.0.20 (Omoch…
…ice#19) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
-
-
Commits on Oct 31, 2023
-
Mostly English spelling and getting rid of deprecated Go functions.
-
chore: refactor code for returning error message
The idea now is to rely more on `net/http` and less on our own internal table.
Commits on Nov 3, 2023
-
-
chore: refactor code to avoid object ambiguities
New code requires passing structs representing JSON objects, instead of relying on loose interface conversions which may fail. Stricter is better!
-
-
Commits on Nov 4, 2023
-
-
-
fix: correctly display versions and build dates
Note: I don’t know where the “builtBy” parameter comes from; currently, it needs to be force-pushed at bildtime with a -X tag to the linker.
-
chore: refactor more code, add option for glossary
This was mostly meant as an experiment which can later be copied & pasted for other very similar options. apiCall() gained a new parameter, the method (because some things in the API stupidly use GET and not POST)
Commits on Nov 9, 2023
-
-
fix: revert changes: init must be done in main()
I’ve attempted to do all initialisation chores under the “Before:” for the main cli.App loop. However, this wasn’t retrieving the data properly. Moving everything back to where it was in main().
-
feat: major refactoring, we’ll get rid of settings
In essence, we can use and reuse the DeepLClient type/object as the ‘de facto’ settings structure, we just need to find a way to read/save settings (possibly with cli-altsrv)
-
-
-
Commits on Apr 12, 2024
-
Correction submitted by @coderabbitai Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
-
-
Bug: fix expected error text for DEEPL_TOKEN
I had changed the text in main.g0, but forgot to update it in main_test.go
-
-
-
-
-
Bug: possible scoping issues with deeplToken (?)
Not confirmed. But… this way we can be sure that it gets properly initialised and not scooped up into the “wrong” place…
-
Merge branch 'GwynethLlewelyn-adding-XML-tag-support' of github.com:G…
…wynethLlewelyn/deepl-translate-cli into GwynethLlewelyn-adding-XML-tag-support
-
Commits on Apr 13, 2024
-
-
-
Chore: add test for Exists; err.Error() is redundant
… at least, when called with the text formatting functions derived from the `fmt` package.
-
-
Fix: check for edge case of empty string
As suggested by @coderabbitai Also: return nil and not []string{}; we’re supposed to check for the `err` code, and nil is returned avoiding memory allocation of something that will never be used…
-
Chore: use http.StatusXXX instead of numbers
It’s more idiomatic that way, even if not necessarily easier to read (everybody knows their HTTP error codes by heart, right? no? well, then perhaps it’s better to follow the usual practice of Go’s core developers…)
-
-
The reason for it was that a potential JSON error was not being correctly caught; this was flagged by the test suite, and therefore I sort of fixed it. Now it correctly passes all tests it’s supposed to pass :)
-
-
Docs: add comment made by @coderabbitai
Future TODO — have `Languages()` optionally reply in structured formats.