Hi all, I would like to report/fix some formatting issue in the doc

# arrow

[ivanmorgillo]

Hi all, I would like to report/fix some formatting issue in the doc

[ivanmorgillo]

https://arrow-kt.io/docs/apidocs/arrow-core/arrow.core/-either/

[ivanmorgillo]

I can't find the doc source code 🤦‍♂️ it's too much Sunday 😂

[raulraja]

hi @ivanmorgillo, we are not sure what’s causing it but we think it may be related to the //sampleStart etc blocks. Feel free to look into it if you want, we are currently focused on releasing 1.0.0 and will look into it after that. I believe the comments can be dropped since we no longer support online playgrounds, so maybe it’s just a matter of rewriting the example to not use those.

[raulraja]

same issue in Option https://arrow-kt.io/docs/apidocs/arrow-core/arrow.core/-option/

[ivanmorgillo]

let's see if I can help 🙂

PS
I added Arrow to a new Compose4Desktop app I'm writing with @seb and I noticed that ! is not working as .bind() in the either {} anymore? I have been away for a bit and maybe I'm "holding it wrong"™. That's why I noticed the issue in the doc 😂

[raulraja]

hahhaa yeah, before 1.0.0 we simplified binding by popular vote to just .bind() which is what most people used and preferred

[ivanmorgillo]

that's fair. I had my share of WTFs from my students trying to explain that syntax:

So it's negating the Either?

No, it's sort of short-circuiting to the right.

And then it's negating it?

No, nobody it negating anything FFS!! 😂

[raulraja]

exactly and the other option which was invoke resulted in many cases in double invokes like f()()

[raulraja]

bind seemed to be the most explicit one and the one people preferred for 1.0.

[ivanmorgillo]

nice 👍

[seb]

@ivanmorgillo you and @pablisco will have a lot of fun at my expense on Weds aren't ya 😂

[ivanmorgillo]

Nah ☺️

[pablisco]

My FP game is a bit off lately, haven't used it in prod for about a year... But it's like riding a bike right? If you forget, you can crash. Is that how the saying goes?

[seb]

Yep 😄