fix: prop access and added test

[Keyrxng]

Resolves #227

• correct prop access typo
• add test for invalidate functionality

[ubiquibot-continuous-deploys[bot]]

25555f1

f6b6f85

eccb5f0

[github-actions[bot]]

Preview Deployment
[25555f1d2b7267a86821633da74930418f611bfa]()
[f6b6f8581ab56185931c6e26ee56e62b146616cf]()
[eccb5f09fa0f475715f59e7e6b143377380e0532]()

[Keyrxng]

CI failed because of nonce too low again

[rndquu]

CI failed because of nonce too low again

Could you merge the latest development branch and try again?

[Keyrxng]

@rndquu all passing, the new setup scripts seem like they are doing the trick. Ofc it could still potentially fail but it's far less likely

[0x4007]

Preview Deployment
[25555f1d2b7267a86821633da74930418f611bfa]()
[f6b6f8581ab56185931c6e26ee56e62b146616cf]()

@gentlementlegen perhaps we should remove this feature because it doesn't work where it's needed. I was going to test the pull now but the link is invalid. Or if you can fix this that would be ideal.

Alternatively we could create a "dev mode" menu on preview deployments to inject a permit. Perhaps we could generate it from the current active wallet so that we could also test invalidation etc. just a thought but also I'm a bit concerned that it's over engineered for the problem we are trying to solve (QA)

Reopened #195

[gentlementlegen]

@0x4007 Sadly back to the problem with the env missing on pull_request unlike pull_request_target. I'll see if we can use the same trick we do for Knip testing, where we trigger another workflow that will get the environment loaded. Otherwise we will have to add a dev mode indeed.