Replace FeatureQuery roles with model types #4941

Closed
opened 2025-12-29 19:22:28 +01:00 by adam · 2 comments
Owner

Originally created by @jeremystretch on GitHub (May 21, 2021).

Proposed Changes

Now that extra features (custom fields, webhooks, etc.) have all been standardized across model types, there's no need to track these individually. We should refactor FeatureQuery to register models based on their parent class rather than a static list of features.

Justification

Simplifies the code base and reduces opportunity for error

Originally created by @jeremystretch on GitHub (May 21, 2021). ### Proposed Changes Now that extra features (custom fields, webhooks, etc.) have all been standardized across model types, there's no need to track these individually. We should refactor FeatureQuery to register models based on their parent class rather than a static list of features. ### Justification Simplifies the code base and reduces opportunity for error
adam added the type: housekeeping label 2025-12-29 19:22:28 +01:00
adam closed this issue 2025-12-29 19:22:28 +01:00
Author
Owner

@jeremystretch commented on GitHub (May 21, 2021):

I should also note that we still need to preserve the ability to register specific features (for plugins). We can just make inferences based on the stock model classifications.

@jeremystretch commented on GitHub (May 21, 2021): I should also note that we still need to preserve the ability to register specific features (for plugins). We can just make inferences based on the stock model classifications.
Author
Owner

@jeremystretch commented on GitHub (Sep 15, 2021):

Going to close this as there hasn't been any progress nor any real impetus for the change.

@jeremystretch commented on GitHub (Sep 15, 2021): Going to close this as there hasn't been any progress nor any real impetus for the change.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4941