Live Refresh of the Panel

[ReeceM]

Naturally, seems it is a bot that is submitting the types via a PR the types can be validated and placed into a pending types branch, currently exists.

So PR is made in the new-types branch, the frontend, because it has multiple deploys can ping the 'pending' endpoint for indexed data, and then redisplay that on the main page.

And because of that, the page could determine what branch it is on and use next to select what to render. Turning the whole static site into a single API that contains it's index. (at this point someone might realize I was talking to myself)

The frontend can have a default set rendered through the static deploy, maybe the latest or 'stared' of a user (stick in localstorage/browser db) no need to collect random junk about them

Then it can query the other branch/webpage instance as a static db as it were. This can then render the all the types or just the pending ones and have them merged to the list.

Possibility:

• the ones in the pending section cannot be downloaded but can be viewed in the issue/PR, if someone wants to use it they can. [maybe upvoted]
• If all are on a single branch and separate from the frontend, then one can have an api that can be queried from a CLI

Mind runs a muck then, no?

[ReeceM]

can use tcp or polling too. 🤷‍♂️