lang: Clearer error when handling not initialized accounts

[cyphersnake]

Close #1015

• Add ErrorCode::AccountNotInitialized
• Add check in Account::try_from & Account::try_from_unchecked

[fanatid]

Since this only more details errors and ProgramAccount / ProgramState are deprecated I do not think that we need a new trait.

[cyphersnake]

@fanatid
I added this trait more for clarification of what I am checking and why, rather than for reuse in deprecated structs. I can clarify this in the comments to the if statement, but as for me this is more bad code practice, than rustdoc.

And to be honest, I just moved our internal trait to anchor, since this is how we check if the account is initialized or not. 😅
Add a reaction: 👍 to this post, if you consider it overkill and I'll remove it in favor of a simple use of if.

[cyphersnake]

I see CI dropped on some tests, I'll figure it out and fix it a little later

[fanatid]

We need a record about a new error in CHANGELOG.md

[fanatid]

It would be nice if we will have a test somewhere for a new error.

[fanatid]

🤔

[cyphersnake]

In the whole CHANGELOG, you don't have single items without a "*" at the beginning. I thought it was a typo and corrected it. Boy Scout Rule 😅

[fanatid]

LGTM, thanks for the test!

[armaniferrante]

The newly added test fails.

[cyphersnake]

The newly added test fails.

Fixed. CI passed

@armaniferrante Is there a way to immediately run tests with updated clients in JS? Or I just need to learn how repos CI do it?

UPD:
@fanatid I understand that most likely it is possible to link a specific js client, cli and everything together and only then run the tests, however, it would be nice to have a command that can do this completely by itself (and without affecting stable version on the env). Through cargo make for example or something similar for yarn. As a last resort via Dockerfile. 49 minutes in CI doesn't seem like the main way to debug an application.

[cyphersnake]

@armaniferrante Do I still need to improve PR somehow? Let me know please

[armaniferrante]

Is there a way to immediately run tests with updated clients in JS? Or I just need to learn how repos CI do it?

I alias the path to my local CLI build and either yarn link or set the file path to the local ts build in the test. Not clean, but it's easy and gets the job done. Would be awesome to see future changes that handled this more elegantly.