-
# Issue
Records are being set in the `ResourceIds` table before emitting the event to register that table in `Tables`.
Without that event indexers are not able to read the `ResourcesIds` schema fro…
-
### ⚠️ Please verify that this bug has NOT been raised before.
- [X] I checked and didn't find similar issue
### 🛡️ Security Policy
- [X] I agree to have read this project [Security Policy](https:/…
-
Store's splice operations on static and dynamic fields use a field index to map to contract storage slots. Without this data expressed in events, offchain clients/indexers are ~forced to model the dat…
holic updated
8 months ago
-
### ⚠️ Please verify that this bug has NOT been raised before.
- [X] I checked and didn't find similar issue
### 🛡️ Security Policy
- [X] I agree to have read this project [Security Policy](https:/…
-
### ⚠️ Please verify that this bug has NOT been raised before.
- [X] I checked and didn't find similar issue
### 🛡️ Security Policy
- [X] I agree to have read this project [Security Policy](h…
-
### Version of Hardhat
2.17.1
### What happened?
When I invoke the call function in nodejs to get a value from the world contract like this
```
const contract = new web3.eth.Contract(worldC…
-
We currently prefix `StoreCore` events with `StoreCore`, but not `World` events/errors. We should align on one approach, and prefixing makes it easier to debug where an event came from.
TODO:
- [x…
-
# Current situation
Store events:
```solidity
event StoreSetRecord(bytes32 tableId, bytes32[] key, bytes data);
event StoreSetField(bytes32 tableId, bytes32[] key, uint8 schemaIndex, bytes dat…
-
Right now we generally use the pattern:
```
namespace (bytes16) + name (bytes16)
```
I am proposing we explore a pattern like:
```
resource type (bytes2) + namespace (bytes14) + name (bytes16)…
-
We currently have some checks in `Store` to confirm that the input data has the correct length etc. To save gas and "not protect the user from themselves" we should remove these checks and expect user…