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

separate AbstractBasePluginModel and it's base functionality #23

Open
benzkji opened this issue Nov 17, 2019 · 1 comment
Open

separate AbstractBasePluginModel and it's base functionality #23

benzkji opened this issue Nov 17, 2019 · 1 comment
Assignees

Comments

@benzkji
Copy link
Member

benzkji commented Nov 17, 2019

ie AbstractBasePluginModelMixin and AbstractBasePluginModel, that form todays AbstractBasePlugin. This would allow to use the basic concept, but without the default fields provided.

The mixin would define a basic API:

  • is_visible
  • str, with usage of self.to_string()
  • add_hidden_flag(text)
  • basic css_classes()
  • basic html_id()
  • html_wrapper_attributes(), using the two above

the model provides:

  • basic (oppiniated) fields, like title, published, layout, color, in_menu, anchor
  • more advanced css_classes, based on the fields
  • some for is_visible
  • inherit from models.Model
@benzkji benzkji self-assigned this Nov 17, 2019
@benzkji
Copy link
Member Author

benzkji commented Aug 6, 2020

note to self: why would this be useful?

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

No branches or pull requests

1 participant