#kdl — Public Fediverse posts

@thezerobit it is not a subject of YAML but #KDL is what I've been looking into using for structured data (e.j. configuration) https://kdl.dev/

@phpcraftdream #KDL is kinda like a command line, check my config here https://github.com/pancsta/secai/blob/main/examples/cook/config.tpl.kdl Ive also written a readable formatter yesterday, as the default one is, well, like a command line https://github.com/pancsta/secai/blob/main/shared/shared.go#L1013

Improvements to the KDL serde API: You can now do boolean-flag children (where an empty child signals a true boolean), as well as #rest for picking up arguments that weren't picked up by #{n} renames. Also, serde errors are now miette Diagnostics too!

#Rust #RustLang #kdl

Пишем движок для блога на Rust

Недавно я решил завести собственный блог. Сначала посмотрел в сторону SSG, но они показались мне не слишком удобными для того сценария, который я хотел получить. Затем попробовал несколько CMS, однако быстро упёрся в другую проблему: мой сервер оказался слишком слабым для большинства современных решений. В итоге ни одно из готовых решений так и не смогло закрыть все мои требования одновременно. Так и появилась идея сделать небольшую файловую CMS на Rust, которая не требует базы данных, не потребляет много памяти и при этом остаётся достаточно гибкой для повседневного использования. Со временем идея небольшого блогового движка разрослась в полноценную CMS с SSR, виртуальной файловой системой, поддержкой локализации, визуальным редактором статей и горячей перезагрузкой контента. В этой статье я постараюсь показать, как всё это устроено изнутри.

https://habr.com/ru/articles/1041324/

#rust #tokio #ssr #vfs #typescript #rxjs #jwt #fluent #kdl

cackles IT LIVES. IT LIVES!!

#rust #rustlang #kdl

I think maybe I'll try and land serde support in kdl-rs tonight?

#kdl #rust #rustlang

Thanks to a couple of community contributors, kdl-rs will soon have proper serde support, with the ability to remap things you want into vecs/fields/etc as you want! It's very similar to how quick_xml does things, if you're familiar with that.

#kdl

I've proposed that the KDL organization move over to Codeberg: https://github.com/kdl-org/kdl/discussions/563

#KDL

[ANN] kdl-hs 1.0.0 released with v2 support

kdl-hs is a parser for the #KDL configuration language, now compliant with the v2 standard.

https://discourse.haskell.org/t/ann-kdl-hs-1-0-0-released-with-v2-support/13712

#Haskell

maybe I'll do some KDL stuff today. As a treat.

#KDL

Initial custom themes support has landed in @conjured.ink's stall software and it's very fast, and very easy to write custom themes for (assuming you know a little bit of HTML/CSS!)

Highlights:

• VERY fast jinja-style templates w/ layouts & partials
• KDL-based metadata ;)
• No framework needed!
• Easy packaging

Our shops are more than just ecommerce: they're going to be able to do newsletters/blogging, POSSE, and general custom websites, all with an EXTREMELY small footprint that will be cheap or free!

Like this whole thing? Please support us if can comfortably do so: https://mastodon.social/@conjured_ink/115347161647458655

#KDL #POSSE #IndieWeb #Rust #RustLang #StopPayPros #BoostsWelcome

Big Brain, btw, is designed to be data-oriented, so I might provide an API that lets you define game AI in .kdl files that look like this. It could also, for example, eventually use a hypothetical node editor (thing Blender Geometry Nodes), to define the same data.

#KDL #Bevy #BigBrain #GameAI

Hold up can we talk about how cute this little file tree icon for KDL files in Zed is?!

#KDL #ZedEditor #Zed

@samir obligatory #KDL spam: https://kdl.dev

Excited for the @bevy scene format. I poked at it a bit and it's definitely something that would look really darn good in #KDL. This is using the proposed number type suffix syntax.

Once the format lands, I might write an adapter that lets you write scenes in KDL and hot reload w/o recompile!

ok hear me out

what if

#KDL args/prop vals could be nodes, too? This seems... tremendously silly, but I can imagine use cases even if I can't imagine how to make it look reasonable.

language design challenge: If you were to support unquoted paths in a language like #KDL, how would you do it in a way that didn't have massive footguns?

See https://github.com/kdl-org/kdl/discussions/494 and send us your answer there! Maybe there's still a way :)

#KDL v2 is such a delight to use omfg

I just really really really wish we had found a good way to allow / in bare idents. One of those sins of the past thing where we would’ve had to completely change the comment syntax to support it :(

Probably my only regret about the language right now tbh.

L'association Le Klan du Loup vous souhaite une très belle fête de Lugnasad 🌾🌾🌻🌻🐾

#KDL

so this is happening.

All my #Rust #RustLang repos are moved over. Now I just need to figure out CI, republish to crates.io, and archive the github side (and document a tombstone in their readmes).

I have a bunch of other repos I'll either archive or delete as well.

#KDL and #orogene will remain github-side for now because they're a bit more dependent on github services, but I would like to at least move orogene over eventually. KDL might be stuck, though, unfortunately, but I might move only kdl-rs.

#bevy #miette

semi-cursed idea: a #KDL representation of _every #XMPP stanza_, mostly for denser raw storage.

Most clients decide very-lossy data storage is good enough, but that doesn't satisfy me. The current storage mechanism for Spades is based on the XML stanzas (in MAM form) and the size of the XML in bytes represented as an ASCII number, wrapped in ASCII record/field separator characters. (Actually, the XML might be gzipped, I can't remember.) To condense it further, I could try to write a dense KDL representation and convert at store and read time. I could also try Brotli instead of gzip or xz.

I'm also thinking I'll want to split the history into multiple files (possibly by file size), and figure out how I'm going to page through that. Also it's all stored unencrypted at rest right now. (I think when I tried to do E2EE last, I had to have it save the unencrypted version because I had no direct access to the original encryption module to re-decrypt it; it's more or less embedded in the SDK and decrypted before I get it.)

#kdl file formatter! Check it out:

https://github.com/hougesen/kdlfmt

secretly genius #xmpp idea: #KDL representation of Data Forms.

So this beast:

      Bot Configuration
      Fill out this form to configure your new bot!
      
        jabber:bot
      
      Section 1: Bot Info
      
      
      
        
      
      
      Section 2: Features
      
        contests
        news
        polls
        reminders
        search
        news
        search
      
      Section 3: Subscriber List
      
        20
        10
        20
        30
        50
        100
        none
      
      Section 4: Invitations
      
        Tell all your friends about your new bot!
      
    

(form)meta {
  title "Bot Configuration"
  instructions "Fill out this form to configure your new bot."
}
(hidden)FORM_TYPE jabber:bot

(fixed)"" "Section 1: Bot Info"
(text-single)botname label="The name of your bot"
(text-multi)description label="Helpful description of your bot"
(boolean)public label="Public bot?" required=#true
(text-private)password label="Password for special access"

(fixed)"" "Section 2: Features"
(list-multi)features label="What features will the bot support?" {
  (option)contests label="Contests"
  (option)news label="News"
  (option)polls label="Polls"
  (option)reminders label="Reminders"
  (option)search label="Search"
  news
  search
}

(fixed)"" "Section 3: Subscriber List"
(list-single)maxsubs label="Maximum number of subscribers" {
  20
  (option)10
  (option)20
  (option)30
  (option)50
  (option)100
  (option)none label=None
}

(fixed)"" "Section 4: Invitations"
(jid-multi)invitelist label="People to invite" desc="Tell all your friends about your new bot!"

Still looking for some help from an extra set of eyeballs or such for some #KDL consistency checking

From: @zkat
https://toot.cat/@zkat/114359709628259341

A request for folks interested in language grammar stuff who might look at the newest #KDL feature and try to poke holes in it: https://github.com/kdl-org/kdl/issues/510#issuecomment-2815654392

Finally managed to go back to my #KDL suffix type annotations PR, and I'm pretty happy with where I've landed so far with the usage criteria, which had gotten a bit hairy. These rules are MUCH more straightforward, and focus on preventing accidentally parsing something successfully as unexpected data, as opposed to yielding a parse error and telling you to use a different syntax.

What do y'all think? Does this make sense?

PR: https://github.com/kdl-org/kdl/pull/513