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

Switch to non-deprecated remote schema referencing #685

Open
2 tasks
cortadocodes opened this issue Nov 14, 2024 · 0 comments · May be fixed by #684
Open
2 tasks

Switch to non-deprecated remote schema referencing #685

cortadocodes opened this issue Nov 14, 2024 · 0 comments · May be fixed by #684
Labels
bug Unintended behaviour in any area of the app

Comments

@cortadocodes
Copy link
Member

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
@cortadocodes cortadocodes added the bug Unintended behaviour in any area of the app label Nov 14, 2024
@cortadocodes cortadocodes linked a pull request Nov 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended behaviour in any area of the app
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant