Andor Penzes

icon indicating a website link patreon.com/AndOrP

icon company https://www.redbubble.com/shop/ap/92458473 icon location London, United Kingdom icon location FP developer who applies formal methods in software engineering, has a colorful experience from Quality Assurance to Proof Engineering.

Results 75 comments of Andor Penzes

Make validation errors translatable

Related to: https://github.com/liqd/aula/pull/752

deleted users are leaking.

Related type: https://github.com/liqd/aula/blob/91f658f9f210695f7071c6cd3c2027eae5dd9858/src/Types/Core.hs#L188

Remove `assert`-s from the code.

I would take a step further, and turn them into some type safety trick.

Remove `assert`-s from the code.

I am ok to have assertion in production for the time being, but for me it is a sign for a missing abstraction that we cover with an `assert`. For...

Remove `assert`-s from the code.

When we have enough data points at the late stage of the project.

PersistNat should capture User as a Parameter for the natural transformation.

I would like to implement this change.

PersistNat should capture User as a Parameter for the natural transformation.

I've encountered use cases of the current user as a parameter for the persistent layer. - Adding data in middle of a transaction, lead the persist broken into 3 transactions,...

PersistNat should capture User as a Parameter for the natural transformation.

An easy workaround for this is to create a similar function to `addWithUser` which has the following type: ``` haskell modifiesWithUser :: ... -> (User -> AUpdate a) -> m...

PersistNat should capture User as a Parameter for the natural transformation.

If you feel so to try that implementation it is good for me. But I would be totally happy with the `User -> AUpdate a` version, as we have to...

review authorization

Related to: https://github.com/liqd/aula/issues/805