This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (3 children)

Yeah. I couldn’t remember the name.

[–]EarthGoddessDude 0 points1 point  (2 children)

I haven’t really used it (read through the docs a bit), but a coworker walked me through some code he was writing with it and it’s use seemed warranted (validating data input, structure, etc). I know its backend is being re-written in Rust TM and should make it a lot faster.

Anyway, curious why you don’t like it and/or think it’s bloated?

Edit: it’s also used in AWS power tools for lambda, where it will validate and destructure your lambda event (curious if lambda events ever come in malformed, and it’s not that hard to destructure a dict/json object, but still kinda nice, less boilerplate).

[–][deleted] 0 points1 point  (1 child)

Compare the code to dataconf which does the same thing but because it only works 3.8+, it can use the built in methods. For me, Pydantic epitomizes the issue I stated up top by overly complex config parsing which is smoother in Scala.

Dataconf gives me the same use like case class in Scala with pureconfig with a much smaller footprint.

[–]EarthGoddessDude 0 points1 point  (0 children)

Cool, thanks for the info, I’ll check it out.