skepller@lemmy.world to Programmer Humor@lemmy.mlEnglish · 2 days agoTOMLlemmy.mlimagemessage-square26fedilinkarrow-up1138arrow-down15file-text
arrow-up1133arrow-down1imageTOMLlemmy.mlskepller@lemmy.world to Programmer Humor@lemmy.mlEnglish · 2 days agomessage-square26fedilinkfile-text
minus-squareell1e@leminal.spacelinkfedilinkEnglisharrow-up2·edit-21 day agoI can’t really decide what extensions my users will face, once they are supported. Therefore too many extensions seems bad to me.
minus-squareEphera@lemmy.mllinkfedilinkEnglisharrow-up2·edit-21 day agoWe just document that this is how you write the config file: [network] bind.host = "127.0.0.1" bind.port = 1234 # etc. And that seems straightforward enough. Yeah, technically users can opt to use inline tables or raw strings or whatever, but they don’t have to.
minus-squareell1e@leminal.spacelinkfedilinkEnglisharrow-up1·20 hours agoConfigs are often shared, just to explain my reservations with TOML. For my project, I used INI instead.
I can’t really decide what extensions my users will face, once they are supported. Therefore too many extensions seems bad to me.
We just document that this is how you write the config file:
[network] bind.host = "127.0.0.1" bind.port = 1234 # etc.And that seems straightforward enough. Yeah, technically users can opt to use inline tables or raw strings or whatever, but they don’t have to.
Configs are often shared, just to explain my reservations with TOML. For my project, I used INI instead.