Change Shadowed Fields on Existing Core Filter Sets

[bryanculver]

Adapted from https://gist.github.com/jathanism/7c585954da4cb1a54997be31991cdaac#coreutilities --

Core/Utilities

Utilities are being included with core since nautobot.utilities.filters.BaseModelSet is the bread and butter here and we may very well end up folding all of the primitives from Utilities into Core to streamline the namespace.

Items that have been moved to their own story:

BaseFilterSet

• The model field to filter field mapping at BaseFilterSet.FILTER_DEFAULTS needs to also include the correct UI widget types in the extra for the filter mapping
  • UI 2.0: /api/ui/ Endpoint for Model, Filterset Definition to Schema #3582
  • Parse Filter Schema Definitions to React Filter Panel Components #3583
• Filter mappings for ALL bespoke field types should be extended
  • For example TaggableManager should always be mapped to TagFilter to obviate the need to define tag/tags on every new filterset that requires tags. (but see also TagFilter created from BaseFilterSet Meta.fields is not using slug #3154)
  • Investigate Model Field Types Coverage in FILTER_DEFAULTS #3584
• The base form used should be included by default on the Meta.form option. This base form should be what is used as the base form for our UI including its own model field to form field mappings. (See field_classes on that page).
  • Most to be done with the JSON schema representation but we may need to somehow provide a way when the schema isn't good enough to specifically provide the react form that represents that model (either by convention in the React packaging or by configuration in the model). Let's start with the schema first.
  • Let's see how much .form is used anymore with the new UI
• Provide Simplified Way to Define Nested Related Fields on FilterSets #3585
• Reverse Related Manager Fields Should Include has_ Filters Automagically #3587
• Rename NameSlugSearchFilterSet to NameSlugSearchFilterSetMixin because it is a mixin #3588

---

Review:

https://gist.github.com/jathanism/7c585954da4cb1a54997be31991cdaac#extras

for fields to be changed under "Incorrect Fields"

NOTE: Let's do this after #2721 and #2722

[bryanculver]

Blocked by #2721 and #2722

[glennmatthews]

Since we decided not to collapse extras into core for the time being, should this be split into two issues? I.e. create a separate issue for the extras filtersets?

[bryanculver]

Done because bullet points were either already done or opened as separate issue, many of which are enhancements and not breaking changes.

💪