skepller@lemmy.world to Programmer Humor@lemmy.mlEnglish · 21 hours agoTOMLlemmy.mlimagemessage-square20fedilinkarrow-up1113file-text
arrow-up1113imageTOMLlemmy.mlskepller@lemmy.world to Programmer Humor@lemmy.mlEnglish · 21 hours agomessage-square20fedilinkfile-text
minus-squareell1e@leminal.spacelinkfedilinkEnglisharrow-up2·edit-210 hours 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-27 hours 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.
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.