Skip to content

Switch to non-deprecated remote schema referencing #685

Open
@cortadocodes

Description

@cortadocodes

Bug report

What is the current behavior?

We're getting/resolving remote JSON schema in a deprecated (and possibly uncached) way

What is the expected behavior?

We resolve once per runtime according to best practice and the cache is used after that.

Proposed Solution

  • Switch to the above approach
  • Test that the schema is being cached

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugUnintended behaviour in any area of the app

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions