Changing the structure of the lists file #8
Replies: 4 comments 7 replies
-
|
This just has the limitation that names can't have |
Beta Was this translation helpful? Give feedback.
-
|
I honestly think they should all be separated, as in the root object is an array and each element is an object with the fields name and what they be shilling. The reason being is multiple certificates (or whatever y'all end up doing) can be made for each thing a person shills, in which case it would make most sense to do the approach I suggested. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome. Add some whitespace so it looks nicer: somehybrid: pathlib
sexnine: cloudflare, sveltekit, jetbrains...and we have not-quite-YAML 😂 |
Beta Was this translation helpful? Give feedback.
-
|
i think the original {
"Anonymous4045": ["linux"],
"sexnine": ["cloudflare", "sveltekit", "jetbrains"]
}is the best imo |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Right now, we are using JSON to store the data. However, what if a user wants to shill multiple things? (looking at you @sexnine). From what I can tell, if we stick with JSON we'd need to make every entry be
"user": ["thing", ...], which seems convoluted to me. I think just havinguser:thing,...in our own structure could be better.looks a lot better to me than
{ "Anonymous4045": ["linux"], "sexnine": ["cloudflare", "sveltekit", "jetbrains"] }Beta Was this translation helpful? Give feedback.
All reactions