Barry

Do you mean just ignore the message or is there mechanism to say "ignore this error specifically"?

This is actually “fixed” in the main branch github.com/kivra/restcl...

#erlang how do I deal with dialyzer errors from dependencies? A type just doesn’t exist in my dependency’s dependency

Picture of the book “A Philosophy of Software Design” by John Ousterhout

Someone suggested this book to me. The preface speaks to me. Hopefully I learn something.

-spec decode_interact_contents(jsx:json_term() | {incomplete, jsx:decoder()}) -> {some, #interact_contents{}} | none. decode_interact_contents( #{ ~"channel_id" := #{~"id" := ChannelId}, ~"user" := #{~"id" := UserId}, ~"team" := #{~"id" := TeamId}, ~"response_url" := ResponseUrl, ~"actions" := #{~"value" := SubmittedUrl} } ) -> {some, #interact_contents{ channel_id = ChannelId, user_id = UserId, team_id = TeamId, response_url = ResponseUrl, submitted_url = SubmittedUrl }}; decode_interact_contents(_) -> none.

I like this a lot better than my previous implementation. It is obvious in hindsight. #erlang

I have one more day but I keep saying “surely kiddo will sleep in tomorrow a bit” and I’ve been WRONG

This is completely untrue. I’ve found so many bugs 😂

Trying to get my project to 100% dialyzed. It’s a labor of love really.

The best part about solo-parenting is waking up at 5:30 am three days in a row.

I suppose I could do nested map pattern matching for the pieces I need and put them into a record?

Can anyone provide me an example of idiomatic jsx usage in #erlang? I have this recursive get function which offers something like `recursive_get([~”outer”, ~”inner”], jsx_term())`. It returns jsx_term() but unsure what y’all do.

“quiet” got me a few days ago.

I’d be willing to bet money the blueberry thing is just someone trolling another person on Reddit which got picked up in the training data.

FWIW, I understand that this shouldn’t be able to work after thinking about it for a bit.

If I _could_ I would 100% write a standard library that is friendly with `maybe`.

It would be sick if I could do `{deps, [{sets, ".*", {git, "https://github.com/chiroptical/s2", {branch, "main"}}}]}.`

Used meck for the first time today. Pretty convenient #erlang

{dialyzer, [ {warnings, [unknown]}, {plt_apps, top_level_deps}, {plt_extra_apps, [uuid, elli, jsx, eunit, ssl]} ]}.

Why do I need to add these dependencies to dialyzer? They are listed in my `deps` section of rebar.config? #erlang

Getting coverage reports from #erlang is so nice.

By ignore, I just mean they end up in the else clause to make the happy path more clear.

In #erlang, a lot of existing APIs return `a | {error, _}`. This is unfortunate when working with `maybe`. I’m considering an EEP which introduces something like ??= to maybe which explicitly ignores error tuples/triples. What do you think?

Looks like relx packaged into a docker container would be simplest?

I’ll probably also re-write it in #gleamlang because I want static types.

Once it is deployed and my friends and I test it out a bit. I’ll share more information.

My #erlang Slack bot is nearly ready to be deployed! If y’all have any deployment docs/blogs you think I should check out please post them 😊

YouTube video by Gears What's new in Gleam 1.12?

Whoa, Gears has made a video overview of Gleam v1.12.0! What a lovely surprise!
www.youtube.com/watch?v=KYvy...

It is done. I really need to re-build this habit. It is ~30-35 minutes of listening plus ~15 minutes of activities. I was doing really well between Jan-April and just fell off.

If I don’t do my Pimsleur lesson today you can slap me the next time you see me.

I’ve become an Old Forester main.

Go learn what my handle means