weird behavior with args.*Result after updating to sapphire v5.3.1

Hello,

I have this code (pls see screenshot) available as

[p]base64

[p]base64

cmd, this same setup worked perfectly fine when I was on sapphire 5.2.1 but after updating to v.5.3.1 today weird issues like these are popping up. Did something change in @sapphire/result to introduce this change? because it feels like breaking.

also I tried to check whats changed between @sapphire/result v2.6.6 ... v2.7.1 but it says 465 files changed and trying to browse it to figure out what changed makes chrome on my potato laptop hard crash, so can someone help me figure out around this issue? thanks.

Solution

- if (getMode.isErr()) getMode = { value: 'decode' };
+ if (getMode.isErr()) getMode = ok('decode');

- if (getMode.isErr()) getMode = { value: 'decode' };
+ if (getMode.isErr()) getMode = ok('decode');

Jump to solution

S-IaF

Sapphire - Imagine a Framework•16mo ago•

54 replies

eon

weird behavior with args.*Result after updating to sapphire v5.3.1

Hello,

I have this code (pls see screenshot) available as

[p]base64

[p]base64

Solution

- if (getMode.isErr()) getMode = { value: 'decode' };
+ if (getMode.isErr()) getMode = ok('decode');

- if (getMode.isErr()) getMode = { value: 'decode' };
+ if (getMode.isErr()) getMode = ok('decode');

Jump to solution

weird behavior with args.*Result after updating to sapphire v5.3.1

Similar Threads

weird behavior with args.*Result after updating to sapphire v5.3.1

Similar Threads

Similar Threads

Similar Threads