John Anderson

That's all fine by me. In most cases, I see only one side being made required. > Should this enforce non-deletion (Ala models.protect)? I say no, not at this time....

> Is "saving" a set of filters, or setting them as per-user defaults for a particular object-list, in scope? No

Sorry, not clear what the specific ask to core is here?

We are thinking a detail route on config contexts should cover this need: ``` GET /api/extras/config-contexts//schema-validate/ ``` This would return something simple like: ```json {"valid": true} ```

@sirtux can you confirm what browser/os and version you are seeing this on?

Actually just confirmed this on https://next.demo.nautobot.com/dcim/devices/?per_page=1000 Seems this is because we load the theme JS after content (which is a general JS best practice), but that is biting us here.

We need to limit this to the scope of fixing the schema. Adding additional functionality like pagination is much harder to in a non-breaking way.

Let's create a spike around investigation of potential issues related to celery task execution.

Somewhat related based on potential chaining of jobs #1292

Closing this out as complete!