After recently releasing version 1.0.0 of @scope42_org and tweeting a lot about the development journey, I think it is time for a more elaborate introduction. Take a look at this blog post if you like to learn more about my software architecture tool ✨ https://t.co/AVPJ4D5wq0
🎉 Milestone Alert! 🚀 docToolchain has hit 100 contributors. We're beyond grateful for this vibrant community that keeps us thriving. 🙏 Thank you, everyone!
Join our celebration by exploring docToolchain today. Start here: https://t.co/BP9Pdr7vGN
#OpenSource#CommunityLove
I made a little demo for teaching the concept of SQL injections to students with little or no programming experience. It is an interactive visualization that is easier to grasp than static PowerPoint slides. Maybe someone else will find this useful, too :) https://t.co/6fgGOD3RXY
Zod 3.20 is here! This is a big one.
🟢 `z.coerce`
🟢 `.pipe()`
🟢 `.catch()`
🟢 `z.symbol()`
🟢 `z.number().finite()`
🟢 `z.string().datetime()`
https://t.co/YHhSLwRhYu
#Langium release 1.0 is coming later this month! As we approach that, we have great stuff to announce.
If you're interested in domain-specific languages or language engineering in general, read these two blog posts about what's happening in the Langium project.
👇
TypeScript 4.9 has landed, and it's a release that's guaranteed to satisfy!
Now bringing
✅ A new 'satisfies' operator
✅ Improved narrowing with 'in'
✅ More efficient file-watching
✅ Better tools import clean-up
and more! Read up now!
https://t.co/7pufSAVu5q
Would be cool to generate some simple Markdown/AsciiDoc from a @structurizr workspace. For example to accompany diagrams with a tabular description of the shown elements - as proposed by @arc42Tipps (https://t.co/IpfuIsMdjU).
I will have a look into this!
@OliverLibutzki > Generating some kind of textual documentation is possible, too.
Yes. For example, the "Structurizr Site Generatr" creates a text-based model explorer if text is your thing -> https://t.co/C5ofzxBHIH
@simonbrown@HerrStachel@structurizr@arc42Tipps Good addition, and that's probably sufficient for a lot of projects. It still is constrained to the output of Generatr.
To clarify my pov, let's say I already have docs somewhere. There I include diagrams from Structurizr. My idea is to extend this to including some text as well.
@HerrStachel@simonbrown@structurizr@arc42Tipps That's also what differs from a holistic approach like Structurizr Site Generatr. Since not all documentation is included in the Structurizr workspace, I'd like to extract information in a form that can be easily embedded elsewhere, e.g. Markdown/AsciiDoc.
@HerrStachel@simonbrown@structurizr@arc42Tipps Yes, this is actually where I'm coming from. A lot of documentation is semi-structured text. But some information is already contained in the model. My idea here is to not only include diagrams but also certain text from Structurizr, e.g. component names and descriptions.