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

refactor: move config tabs method in GlobalConfig class #1595

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

hetangmodi-crest
Copy link
Contributor

Issue number:
ADDON-78036

PR Type

What kind of change does this PR introduce?

  • Feature
  • Bug Fix
  • Refactoring (no functional or API changes)
  • Documentation Update
  • Maintenance (dependency updates, CI, etc.)

Summary

Made config_tabs (which is a method in global_config_validator.py) as a part of GlobalConfig class.

Changes

Made the config_tabs method part of the GlobalConfig class and renamed the previous tabs method in GlobalConfig to configuration.

User experience

Checklist

If an item doesn't apply to your changes, leave it unchecked.

@hetangmodi-crest hetangmodi-crest marked this pull request as ready for review February 20, 2025 10:31
@hetangmodi-crest hetangmodi-crest requested a review from a team as a code owner February 20, 2025 10:31
@hetangmodi-crest hetangmodi-crest self-assigned this Feb 20, 2025
@artemrys artemrys changed the title chore: move config tabs method in GlobalConfig class refactro: move config tabs method in GlobalConfig class Feb 20, 2025
@artemrys artemrys changed the title refactro: move config tabs method in GlobalConfig class refactor: move config tabs method in GlobalConfig class Feb 20, 2025
@@ -122,16 +122,25 @@ def inputs(self) -> List[Any]:
return self._content["pages"]["inputs"]["services"]
return []

@property
def configuration(self) -> List[Any]:
Copy link
Member

Choose a reason for hiding this comment

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

hm, should this be tabs and the one config_tabs would be resolved_tabs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The name tabs was an ambiguous name for the method. The reason for naming it configuration is to maintain parity in global_config.py - since we have an input method (which returns input data) and a pages method (which returns page data), I thought to rename tabs to configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants