| Time |
Nick |
Message |
| 02:08 |
|
Warr1024 joined #luanti-docs |
| 02:10 |
|
user333_ joined #luanti-docs |
| 02:11 |
|
user333_ joined #luanti-docs |
| 02:28 |
|
user333_ joined #luanti-docs |
| 02:49 |
MTDiscord |
<mark.wiemer> sounds great π |
| 02:49 |
MTDiscord |
<mark.wiemer> (^ RE for-server-hosts/setup being a landing page... still catching up on the rest of the convo) |
| 02:51 |
MTDiscord |
<mark.wiemer> And don't think I've forgotten about the docs schema π I'm still sorting out my priorities for January but Luanti is high up there, should be able to contribute a lot in a few days once I clear out some Mocha and CASA work π |
| 05:00 |
|
MTDiscord joined #luanti-docs |
| 17:41 |
|
MTDiscord1 joined #luanti-docs |
| 18:00 |
|
mrcheese joined #luanti-docs |
| 19:06 |
|
mrcheese joined #luanti-docs |
| 22:48 |
MTDiscord |
<mark.wiemer> been doing some research, ref https://github.com/luanti-org/docs.luanti.org/issues/296#issuecomment-3702989432, tldr: Teal is out, not expressive enough. Next steps are to research EmmyLua and YAML, and I expect to rule them out honestly but need to give them a fair shot. Β In parallel, I'll research the entire API file for what sort of things our new canonical form needs to be able to express. @a.corp.serot 's earlier gist was |
| 22:48 |
MTDiscord |
super helpful here and I'll certainly need feedback on this given my minimal real-world experience with Luanti! |
| 22:55 |
MTDiscord |
<a.corp.serot> doing it in YAML is actually very annoying and faces the same problems with markdown approach (you need to make an AST and a verifier) |
| 22:55 |
MTDiscord |
<a.corp.serot> the part that surprised me was the annoying part |
| 22:56 |
MTDiscord |
<a.corp.serot> one of the main issue i had was that the indentation very easily gets out of control. i limited myself to specify a single class (ObjectRef) |
| 22:57 |
MTDiscord |
<a.corp.serot> maybe you'll come up with a better YAML format than i did https://github.com/corpserot/luanti-api-spec/ |
| 23:01 |
MTDiscord |
<a.corp.serot> i think a question that needs answer is: should we even make our own type system, or just adopt an existing one? i'm partial to both, but i think practicality would favor the latter |
| 23:02 |
MTDiscord |
<a.corp.serot> (that would mean we just use something like typescript) |
| 23:15 |
MTDiscord |
<mark.wiemer> yeah TypeScript is on the backlog for that reason, the major downside to TypeScript is that it's likely unfamiliar to Lua devs. But again, whatever canonical form we choose can easily be automatically transformed into a more readable Markdown document later π Β are there other type systems beyond TypeScript or the ones I've listed that you'd want to consider? |
| 23:32 |
MTDiscord |
<a.corp.serot> not really. you ruled out teal, and the only other similar thing i used is emmylua |
| 23:32 |
MTDiscord |
<a.corp.serot> emmylua and luals/luacats |
| 23:37 |
MTDiscord |
<mark.wiemer> Cool, just making sure. I'll probably move TS into the researching phase soon |
