I was very startled, because we just found a function with tests in HedgeDoc 1.😱
Moment later I recovered. The tests were written by @claudius as part of the codimd maintenance.
#hedgedocleaks — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #hedgedocleaks, aggregated by home.social.
-
Myself and @emcrx just had a very productive meeting with a UI/UX designer discussing HedgeDoc 2’s interface. We’ve got some great new ideas from that and will definitely try to improve our UI further on the road to HedgeDoc 2.0.
-
OH “Das sieht auf den ersten Blick so aus als ob die Assembler können?” … “Hä? Was hat Assembler mit fastify zu tun?” … “Das sieht so aus als ob die SemVer können. Keine minor updates mit breaking changes”
Zuhören … kann ich.
-
“Just a moment. Why does it say buildroot in the HedgeDoc release checklist there?”
“Did you not know? There is now a GNU/Linux/HedgeDoc distro.” -
Current state of affairs:
- 1x IDE / JVM crash
- 2x PRs merged for HedgeDoc 1
- 1x HedgeDoc 1 Release pending
- Number of socket.io docs read: too many -
HedgeDoc Weekend Let‘s go! #HedgeDocLeaks #MollyFaehrtBahn
-
Working on #HedgeDoc 1 code is always a test of patience. “How long can I endure this until I start rewriting this function / file?”
-
Two hours down the drain. Thanks “artificial intelligence”. People trying to contributing via AI is so much fun as a maintainer. 🫠
-
-
HedgeDoc just did the fastest support in our history. Report to fix in ~25 min. And it was totally random that that worked out like this. :D
-
“Looks like all browsers are supported. … except for IE. And you know what I can live with not supporting IE.”
#HedgeDocLeaks -
My software architecture prof would be proud of us today. We wrote a full length proposal for how to deal with a complicated problem with multiple solutions and pro and contra lists and we used a truth table to understand a delicate permission problem with unique edge cases.
-
After questioning the library and the mocker library, looking at their bug trackers and contemplating how to communicate with the devs of those libraries, I checked the mocked variables and it turns out the problem was between the monitor and my chair.
And this dear children is why you should always start debugging by checking your basics and not assume that you did everything correctly. -
We just confirmed:
Our database does not do anything, if the function that actually does stuff is not called. We’re very contend with those test results. -
And it's time for a HedgeDoc 1 Release. How did this work again?
-
We at more than one occasion included some “This should never happen.” error messages in HedgeDoc2. Always funny when they then occur despite our insistence that that is not possible. Normally this happens in testing setups where some component is missing for something similar, but funny either way.
-
Today we had so much fun with all the differences between different databases and how they are all slightly different when throwing the exact same code against the different drivers. So much fun. #HedgeDocLeaks
-
Currently working on HedgeDoc 2 with @emcrx and it’s so nice when past us thought things through for us.
“Ups the variable should be named differently.” -
The “Now that we done this, everything should work”-Counter is currently at 21.
-
HedgeDoc Dev-Weekend is going great.
We‘re really close of finally ditching typeorm for good and using knex.
Also the number of "I want to bite in my desk" incidents is the same as the number of times we got cake, so it all averages out.
#HedgeDocLeaks -
“Electric Playing card” HedgeDoc guest username are always great. #HedgeDocLeaks
-
The realisation of the evening: Molly is in fact not an IDE.
-
Ah ja, die bekannte Arbeitsgemeinschaft Polen Lizenz.
-
The new HedgeDoc 2 Stack is Next.js, Nest.js, knex.js and i18next. As you can see it’s very easy to differentiate between all the different frameworks and libraries.
#HedgeDocLeaks #JustJSThings -
-
-
-
“Why isn’t this working correctly it changes in the one direction, but it doesn’t change back. Makes no sense!
[...]
Oh the else case has ToDo comment. Well that explains it!” -
I’m currently learning more about `@media print` and other printing tricks for Browsers than I ever imagined I’d need. #HedgeDocLeaks
-
What will we do today, Brain? The same thing we do everyday, Pinky: Release HedgeDoc 1.10.0.
#HedgeDocLeaks -
OH: Heiße JavaScript-Engines in deiner Nähe! #hedgedocleaks
-
OH: Wir mergen das, releasen das und dann testen wirs. #hedgedocleaks
-
Look at @innaytool developing HedgeDoc 2 on a totally normal setup.
#HedgeDocLeaks -
“These are schrödingers authorship information.” “Yes, and sometimes the text belongs to the cat and I don’t know why😭” #HedgeDocLeaks
-
“Wie bist du da drauf gekommen?”
“Ich habe mein Hirn benutzt!”
“Nein! Jetzt wirklich! Wie bist du drauf gekommen?”
-
“Es gibt jetzt um diese Uhrzeit ein Moratorium auf komische Bugs.” #HedgeDocLeaks
-
We just had a big problem with #CodeMirror highlighting and were not able to find a solution beside removing it all together. So we did that and opened an issue with them in the hope to get this resolved in a few days. The correct answer was given in 3 minutes. On a Sunday. Best support ever!
-
“Look we just remove the syntax at the end and it looks much better immediately.” - “Yes, nobody needs syntax anyway”