fix: return error for non-existent states + unit tests #101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #100
Part of: #79
Description
In this PR, all reader methods have been reviewed to ensure they handle non-existent states by returning an error. However, in a few specific cases, such as when minting a token and needing to check if it has been previously created (exists), we return an optional value due to the internal logic dependency on that state.
Additionally, unit tests were added to cover cases where a state does not exist on storage calls.