feat/seasonModel

[Bosun-Josh121]

closes #89

implemented seasonModel & manager with tests

Summary by CodeRabbit

• Bug Fixes

  • Removed obsolete contract definitions and interfaces to streamline the codebase.

• New Features

  • Introduced a new module for managing seasons within the game.

• Chores

  • Deleted outdated configuration files and model definitions to improve project organization and maintainability.

[coderabbitai]

Walkthrough

The pull request involves the removal of multiple JSON and TOML configuration files related to the ByteBeasts project. This includes the deletion of files that defined various models, contracts, and their associated interfaces, structs, enums, and events. Key components removed include tournament systems, player models, and configurations for actions such as spawning and moving within the game. The changes also include the removal of the MIT License and README documentation, which provided foundational information and guidelines for the project. Additionally, a new module named season has been introduced in the src/lib.cairo file, indicating the start of a new feature related to managing in-game seasons. Overall, the changes signify a significant restructuring of the codebase, focusing on removing existing functionalities while initiating the groundwork for new features.

Assessment against linked issues

Objective	Addressed	Explanation
Implement a Season model and associated functions (89)	✅

Possibly related issues

• Add unit tests for the season PoC model and functions #90: This issue focuses on adding unit tests for the season model and its functions, which aligns with the new season module introduced in this PR.

Possibly related PRs

• Add tests for tournament_system #101: This PR involves the removal of tournament-related structures and interfaces, while the related PR adds tests for the tournament system, indicating a connection to the functionalities described in this PR.

Suggested labels

documentation

Suggested reviewers

• danielcdz
• RolandoDrRobot
• coxmars

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[RolandoDrRobot]

could you please add a pic of the outputs of

• sozo build
• sozo test
  to make sure all previous and current code is good? thank you!

[coxmars]

@Bosun-Josh121 Appreciate your effort on this, looks good to go! Just resolve the conflicts, and we’re ready to merge. 🚀