Go to file
philipp 94a52b94dc
All checks were successful
CI/CD Pipeline / test (push) Successful in 2m25s
clean up repo
2024-02-06 11:30:28 +01:00
.gitea/workflows no db in this project (so far) 2024-01-26 17:24:00 +01:00
data add configs for laws 2024-02-06 11:18:40 +01:00
src clean code with clippy 2024-02-06 11:21:52 +01:00
.gitignore empty rust project 2023-11-03 13:45:25 +01:00
.gitlab-ci.yml run live test on ci 2023-11-06 13:36:33 +01:00
Cargo.lock add config for law texts, fixes #3 2024-02-06 10:17:14 +01:00
Cargo.toml add config for law texts, fixes #3 2024-02-06 10:17:14 +01:00
download_all_pars_from_list.sh create test for full urhg for overview parsing 2023-11-06 12:00:20 +01:00
README.md clean up repo 2024-02-06 11:30:28 +01:00

Add new law text

Tests

  • Getting paragraphs from law_id (risparser::overview::test::parse())
    • Create file law_id in ./data/expected/overview (then run tests to get current output + save in file)
  • Create config file in ./data/configs/

Integration test

  • Nice test would be to re-create html ris file and compare it (problem with custom fixes, though)

Goals

  • I want to have the text of the law.
  • I want to see the structure (proper headers) of the law.
  • I want to be able to make comments (e.g. Erschöpfung) on certain parts
  • I want to see since when this paragraph is in use.
  • [.] Lawtext should be updateable

Mindset

  • I don't want to restrict myself with a parser combinators but code it myself using recursive descent parser.
  • Be strict in what I process. Fail if anything unexpected happens. The user should handle this case. It's fine if one decides to ignore the new/unexpected field, but it should be done deliberately.

Nomenclature

  • Law ("Gesetz"): e.g. UHG, TEG, ABGB
  • Section ("Paragraph")
  • Subsection ("Absatz")
  • Item ("Ziffer")
  • Heading-{1,2,3,...}

Folder-Structure of this repo

  • ./data
    • cache -> cache for overview tests
    • expected
      • overview -> expected xml links of law_ids

History