Monorepo for wisp.place. A static site hosting service built on top of the AT Protocol. wisp.place

suggestion: site name should be case insensitive #40

Closed nekomimi.pet
Closed opened by nekomimi.pet

Thanks to a f# up of my own, I came to the realization that the site name argument for the Wisp CLI is case sensitive, and the back-end is as well. This means that mySite, MySite, and mysite would be 3 different Wisp sites.

Unbeknownst to past (5 minutes ago) me, this was what was keeping me randomly raging at my Tangled pipelines... I kept adding build parameters and removing files to make sure I wasn't hitting limits. Until I opened the Wisp dashboard and noticed I had 2 similarly named sites. One capitalized and one not...

I had initially created the site with a capital letter, as in a title, but used lowercase in my config (because of habit with parameters). So for the past few days, I kept deploying my "fixes" to a totally different site I didn't realize even existed.

Since, in my personal opinion, it doesn't make a lot of sense to have e.g. mySite, MySite, and mysite; I want to propose to make site names case insensitive. By making all site names lowercase in the back-end, you wouldn't run into this issue anymore. Optionally the site identifier and site "title" could be made 2 separate fields in the database such that users can still pick a cased title, while in the back-end the "identifier" would be lowercase.

I guess i can force normalization on the clients. I do think that rkey and Rkey should be fundamentally treated as different records, but yeah, the client itself can normalize rkeys into lowercase

my girlfriend fixed it, thanks for filing

Sign up or Sign in to add to the discussion.