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

Core: move OptionGroup definition to Options.py #3325

Merged
merged 3 commits into from
May 19, 2024

Conversation

beauxq
Copy link
Collaborator

@beauxq beauxq commented May 18, 2024

What is this fixing or adding?

BaseClasses.py doesn't seem like the right place for this.

  • BaseClasses.py was otherwise untouched by the PR that introduced this feature
  • World devs have already noticed that it's nicer to define their OptionGroups in their world's options module, which often doesn't import anything else from BaseClasses.py
    • Adding BaseClasses to those imports increases the risk of having to deal with circular import issues.

How was this tested?

opened an option page from WebHost, observed the option groups, generated a game from the option page

@github-actions github-actions bot added affects: core Issues/PRs that touch core and may need additional validation. waiting-on: peer-review Issue/PR has not been reviewed by enough people yet. labels May 18, 2024
This was referenced May 18, 2024
@PoryGone
Copy link
Collaborator

Seems like a sensible change. If this is going to happen, now is the time, before a bunch of worlds use this feature.

Options.py Outdated Show resolved Hide resolved
Options.py Outdated Show resolved Hide resolved
Options.py Outdated Show resolved Hide resolved
Copy link
Collaborator

@Exempt-Medic Exempt-Medic left a comment

Choose a reason for hiding this comment

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

Change makes sense and fixes what I thought was an unusual decision. Tested it locally, it worked.

@Exempt-Medic Exempt-Medic added waiting-on: core-review Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer. and removed waiting-on: peer-review Issue/PR has not been reviewed by enough people yet. labels May 18, 2024
@Berserker66 Berserker66 merged commit 230a9e6 into ArchipelagoMW:main May 19, 2024
16 checks passed
jnschurig pushed a commit to Tranquilite0/Archipelago-SoulBlazer that referenced this pull request Jun 13, 2024
sflavelle pushed a commit to sflavelle/Archipelago-tgc that referenced this pull request Jun 20, 2024
qwint pushed a commit to qwint/Archipelago that referenced this pull request Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: core Issues/PRs that touch core and may need additional validation. waiting-on: core-review Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants