fix(dojo-core): ensure contract deployment verifies if the selector is unregistered

[glihm]

Summary by CodeRabbit

• New Features

  • Introduced a new error handling capability for resource registration with a function that indicates when a resource is already registered.
  • Added checks to prevent the registration of resources that are already registered, improving resource management.

• Bug Fixes

  • Updated various contract addresses and hashes to ensure correct interactions within the application.

• Chores

  • Modified configuration files to reflect updated class hashes and addresses for multiple contracts, enhancing deployment accuracy.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

Commits

Files that changed from the base of the PR and between 87ad4ab and e63944f.

Files ignored due to path filters (2)

• spawn-and-move-db.tar.gz is excluded by !**/*.gz
• types-test-db.tar.gz is excluded by !**/*.gz

Files selected for processing (9)

• crates/dojo-core/src/world/errors.cairo (1 hunks)
• crates/dojo-core/src/world/world_contract.cairo (1 hunks)
• crates/dojo-lang/src/manifest_test_data/compiler_cairo/manifests/dev/base/dojo-world.toml (1 hunks)
• crates/sozo/ops/src/tests/model.rs (1 hunks)
• examples/spawn-and-move/dojo_dev.toml (1 hunks)
• examples/spawn-and-move/manifests/dev/base/dojo-world.toml (1 hunks)
• examples/spawn-and-move/manifests/dev/deployment/manifest.json (6 hunks)
• examples/spawn-and-move/manifests/dev/deployment/manifest.toml (5 hunks)
• examples/spawn-and-move/manifests/release/base/dojo-world.toml (1 hunks)

_________________________________________________________________
< I have no memory of this place...but I'll find the bugs anyway. >
-----------------------------------------------------------------
 \
  \   \
       \ /\
       ( )
     .( o ).

Tip

You can validate your CodeRabbit configuration file in your editor.

If your editor has YAML language server, you can enable auto-completion and validation by adding # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json at the top of your CodeRabbit configuration file.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.47%. Comparing base (78250fa) to head (e63944f).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2473      +/-   ##
==========================================
- Coverage   68.48%   68.47%   -0.01%     
==========================================
  Files         368      368              
  Lines       48180    48183       +3     
==========================================
- Hits        32994    32993       -1     
- Misses      15186    15190       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.