@@ -197,22 +197,22 @@ so when using `somesy` with pre-commit, keep in mind that
197197
198198Here is an overview of all the currently supported files and formats.
199199
200- | Input Formats | Status | | Target Formats | Status |
201- | -------------- | ------ | --- | ----------------------------------- | ------ |
202- | (.)somesy.toml | ✓ | | pyproject.toml _(poetry v1 and v2)_ | ✓ |
203- | pyproject.toml | ✓ | | pyproject.toml _(setuptools)_ | ✓(1.) |
204- | package.json | ✓ | | package.json _(JavaScript)_ | ✓(2.) |
205- | Project.toml | ✓ | | Project.toml _(Julia)_ | ✓ |
206- | fpm.toml | ✓ | | fpm.toml _(Fortran)_ | ✓(3.) |
207- | | ✓ | | pom.toml _(Java)_ | ✓(4.) |
208- | Cargo.toml | ✓ | | Cargo.toml _(Rust)_ | ✓ |
209- | | | | mkdocs.yml | ✓(5.) |
210- | | | | CITATION.cff | ✓ |
211- | | | | codemeta.json | ✓(6.) |
200+ | Input Formats | Status | | Target Formats | Status |
201+ | -------------- | ------ | --- | ---------------------------------------- | ------ |
202+ | (.)somesy.toml | ✓ | | - | ✓ |
203+ | pyproject.toml | ✓ | | pyproject.toml _(setuptools and poetry)_ | ✓(1.) |
204+ | package.json | ✓ | | package.json _(JavaScript)_ | ✓(2.) |
205+ | Project.toml | ✓ | | Project.toml _(Julia)_ | ✓ |
206+ | fpm.toml | ✓ | | fpm.toml _(Fortran)_ | ✓(3.) |
207+ | | ✓ | | pom.toml _(Java)_ | ✓(4.) |
208+ | Cargo.toml | ✓ | | Cargo.toml _(Rust)_ | ✓ |
209+ | | | | mkdocs.yml | ✓(5.) |
210+ | | | | CITATION.cff | ✓ |
211+ | | | | codemeta.json | ✓(6.) |
212212
213213**Notes:**
214214
215- 1. note that `somesy` does not support setuptools _dynamic fields_
215+ 1. note that `somesy` does not support setuptools or poetry _dynamic fields_
2162162. `package.json` only supports one author, so `somesy` will pick the _first_ listed author
2172173. `fpm.toml` only supports one author and maintainer, so `somesy` will pick the _first_ listed author and maintainer
2182184. `pom.xml` has no concept of `maintainers`, but it can have multiple licenses (somesy only supports one main project license)
0 commit comments