Hydra configuration editor crashes

[tomekpapiernik]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

Trying to access the Hydra config editor the page crashes.

https://www.ory.sh/docs/hydra/reference/configuration-editor

Originally reported by a community member:
https://ory-community.slack.com/archives/C012RBW0F18/p1648498590345789

Reproducing the bug

1. go to https://www.ory.sh/docs/hydra/reference/configuration-editor
2. enjoy the show

Relevant log output

No response

Relevant configuration

No response

Version

current

On which operating system are you observing this issue?

No response

In which environment are you deploying?

No response

Additional Context

No response

[gen1us2k]

I found the issue that causes a webpage crash. The reason lies in spec/config.json. I fixed this with this patch

diff --git a/spec/config.json b/spec/config.json
index 0e8b7baa..c5ea89c6 100644
--- a/spec/config.json
+++ b/spec/config.json
@@ -1214,11 +1214,9 @@
     },
     "dangerous-allow-insecure-redirect-urls": {
       "type": "array",
-      "items": [
-        {
+      "items": {
           "type": "string"
-        }
-      ],
+      },
       "title": "Disable HTTPS enforcement for the provided redirect URLs.",
       "description": "DO NOT USE THIS IN PRODUCTION - Disable HTTPS enforcement for the provided redirect URLs. This is only available as CLI flag `--dangerous-allow-insecure-redirect-urls`."
     }

Also, I found that we use the master branch for config editors. I see two possible solutions:

1. use tags instead of master branch for configuration references
2. Fix config.json generators

[tomekpapiernik]

@gen1us2k
I see that the page still fails whenever you try to access it. Could you please make sure that this behavior is fixed? Any other improvements or updates can be added in subsequent PRs. Thanks!

[gen1us2k]

@tomekpapiernik PR is opened.