Carlos Fernando Baptista

Formalize the non-functional requirements on Release Notes for the version 1.0 release of wflow in the [DoD](https://github.com/Deltares/Wflow.jl/issues/393). ### Tasks - [x] Propose non-functional requirements in DoD - [x] Decide with...

Formalize the non-functional requirements on Known Issues for the version 1.0 release of wflow in the [DoD](https://github.com/Deltares/Wflow.jl/issues/393). ### Tasks - [x] Propose non-functional requirements in DoD - [x] Decide with...

Formalize the non-functional requirements on Actions After Release for the version 1.0 release of wflow in the [DoD](https://github.com/Deltares/Wflow.jl/issues/393). ### Tasks - [x] Propose non-functional requirements in DoD - [x] Decide...

### Wflow version checks - [X] I have checked that the issue still exists on the latest versions of the docs on `master` [here](https://github.com/Deltares/Wflow.jl) ### Kind of issue Docs are...

This PR adds configuration files for both Julia Formatter and VS Code in order to format Julia source files according to the [default style](https://docs.julialang.org/en/v1/manual/style-guide/) (with some minor deviations, see [`.JuliaFormatter.toml`](https://github.com/Deltares/Wflow.jl/blob/refactor/style-guide/.JuliaFormatter.toml))...

Enforce style guide for Julia code

6

Currently, there is no style guide for wflow's Julia code. For improved code quality a consistent style across the team is needed. The most popular style guides in the Julia...

The initialization function for the sediment model is very long. For readability and reuse of code it must be broken down into multiple smaller functions. Along the way unit tests...

Refactor the initialization of the river part of the sediment model