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

Move form feature mixin classes from extras to netbox #14326

Closed
jeremystretch opened this issue Nov 22, 2023 · 0 comments
Closed

Move form feature mixin classes from extras to netbox #14326

jeremystretch opened this issue Nov 22, 2023 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Milestone

Comments

@jeremystretch
Copy link
Member

Proposed Changes

Move the following classes from extras.forms.mixins to netbox.forms.mixins:

  • CustomFieldsMixin
  • SavedFiltersMixin
  • TagsMixin

Justification

This will clean up the form hierarchy a bit, and help avoid circular imports. We currently have a hack in place specifically to avoid this:

# TODO: Removing this import triggers an import loop due to how form mixins are currently organized
from .forms import ConfigRevisionForm

Additionally, it has come up again during work on #14312.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user labels Nov 22, 2023
@jeremystretch jeremystretch added this to the v3.7 milestone Nov 22, 2023
@jeremystretch jeremystretch self-assigned this Nov 22, 2023
jeremystretch added a commit that referenced this issue Nov 22, 2023
* Move form mixins from extras app to netbox app

* Remove obsolete extras/admin.py
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Projects
None yet
Development

No branches or pull requests

1 participant