this is when im starting to head bang a lot, because of an undocumented github feature ive been relying on for web ui editor.

last commit hashes:

• website: f1e3a4387e6780d61bc55feeead37ead03ec3b0a
• register: 5625239d30e691ace298336953d663b6e396c0e3

so ive been using github’s REPO/new/branch/PATH?filenam=A&value=B query params for prefilling records in the web ui editor form. during testing, i noticed that for some reason JSON.stringify isnt formatting the json when i open it on github.

after a bit of testing, turns out github minifies valid json input. when i tried some string concats with JSON.stringify output that produced invalid json then the indentation returns. this is rather confusing and frustrating.

even tho the ci now handles formatting, its still a pain for pr reviewing to review unformatted, one-line json files. due to github not really documenting this feature well, i suppose we have to live with it.

i do have plans later to possibly use octokit instead for pr generation, but thats a lot more work i dont have time for.

anyways, i didnt feel like writing changelog so ill just say it in brief. i added email regex checks to the ci as well as formatting warnings. and for the web ui, i made an advanced view to show raw json and the file path in case someone is willing to do it themselves. i also fixed a lot of the unserious things i threw around the success page like the ??? step