Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(store): revert if slice bound is invalid [L-10] #2034

Merged
merged 5 commits into from Jan 18, 2024
Merged

fix(store): revert if slice bound is invalid [L-10] #2034

merged 5 commits into from Jan 18, 2024

Conversation

dk1a
Copy link
Member

@dk1a dk1a commented Dec 6, 2023

No description provided.

Copy link

changeset-bot bot commented Dec 6, 2023

🦋 Changeset detected

Latest commit: 8bcee1c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 30 packages
Name Type
@latticexyz/store Patch
@latticexyz/cli Patch
@latticexyz/dev-tools Patch
@latticexyz/react Patch
@latticexyz/store-indexer Patch
@latticexyz/store-sync Patch
@latticexyz/world-modules Patch
@latticexyz/world Patch
@latticexyz/abi-ts Patch
@latticexyz/block-logs-stream Patch
@latticexyz/common Patch
@latticexyz/config Patch
create-mud Patch
@latticexyz/ecs-browser Patch
@latticexyz/faucet Patch
@latticexyz/gas-report Patch
@latticexyz/network Patch
@latticexyz/noise Patch
@latticexyz/phaserx Patch
@latticexyz/protocol-parser Patch
@latticexyz/recs Patch
@latticexyz/schema-type Patch
@latticexyz/services Patch
@latticexyz/solecs Patch
solhint-config-mud Patch
solhint-plugin-mud Patch
@latticexyz/std-client Patch
@latticexyz/std-contracts Patch
@latticexyz/store-cache Patch
@latticexyz/utils Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@@ -10,6 +10,7 @@ interface IStoreErrors {
error Store_InvalidResourceType(bytes2 expected, ResourceId resourceId, string resourceIdString);

error Store_InvalidDynamicDataLength(uint256 expected, uint256 received);
error Store_InvalidBounds(uint256 start, uint256 end);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thoughts on Store_InvalidSlice or Store_InvalidSliceBounds?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from @alvrs

no strong opinions, i'm happy with InvalidBounds, or InvalidSliceBounds (think "bounds" in there is nice for consistency with the "out of bounds" error)

alvrs
alvrs previously approved these changes Jan 18, 2024
@holic holic changed the title fix(store): emit custom error if slice bound is invalid [L-10] fix(store): revert if slice bound is invalid [L-10] Jan 18, 2024
@holic holic merged commit 7b28d32 into main Jan 18, 2024
12 checks passed
@holic holic deleted the dk1a/L-10 branch January 18, 2024 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants