Richard Eckart de Castilho
Richard Eckart de Castilho
Refactor conversions into more reusable/uniform units. E.g. have classes called "X2Y" with a method "convert(source, target)".
Add support for document-level key-value metadata. I imagine something like this: ``` === Variant 1 MetaDataEntry extends Annotation { String: key String: value } // Simplest option only allowing String...
Better support for CoNLL-U v2: - [ ] document boundary (`# newdoc`) - [ ] document ID (`# newdoc id = mf920901-001`) - [ ] paragraph boundary at sentence beginning...
Move bibliography references from JavaDoc into OMTD-SHARE annotations (?) and pick them up from there as well when generating the reference documentation (?)
Handle discontinuous segments in brat format. For the moment, at least ignore them/warn.
**What's in the PR** - Manage dependencies in requirements files - Use pip-tools to manage dependencies - Remove poetry **How to test manually** * Build / release **Automatic testing** *...
**What's in the PR** - Remove setup.py - Switch to pyproject.toml - Update GitHub actions to use poetry - Clean up code a bit according to feedback from flake8 -...
**Describe the refactoring action** Address some linter issues. **Expected benefit** Cleaner code.
**Describe the refactoring action** Instead of using poetry, use a plain `pyproject.toml` without `setup.py` but use `pip-tools` to pin requirements. **Expected benefit** Simpler build?!
**Describe the refactoring action** Switch to poetry and pyproject.toml. **Expected benefit** Align with pycaprio and I kind of like the declarative nature of pyproject.toml vs the setup.py.