Macros are one thing I enjoy using the most in #Laravel. It's a way to extend the functionality of many built-in #Facades by providing custom callbacks for a specific key.
One production example I use macros for fairly often is what I call the "admin alert". Especially in smaller applications I want to get notified whenever an error or an event occurs the admin (mostly that's me) should know about.
Mastodon #jerecrute ! Une asso dont je suis membre cherche à refaire son site internet, avec un CMS libre tant qu'à faire, plutôt sur SPIP. est ce que vous connaissez des boites qui propose des presta sur SPIP ? #webdev
I so much want to use this #Hexo theme but translating site with Google Translate is making it hard lol. Can anyone here help me with it ? #Foss#Theme#WebDev
Here's another interesting #HTML tag. <mark> lets you highlight certain parts of your text to draw extra attention to it.
One real world example where this can be especially useful is highlighting the parts of your search results that match the search query. Or at least that's where I regularly use it.
Do you know the #HTML tags 'details' and 'summary'? I didn't until now.
The combination of those two let's you toggle content with default HTML behavior. This is one of those things you will probably not use in production because it just doesn't look so nice but as always, for quickly prototyping something like an FAQ section this might just fit in perfectly.
Got a Playwright question - in my tests I'm clicking a button which in the backend sends an email. I tried to use Jest to mock that function in the backend so it doesn't send an email, but that doesn't seem to work. Should it?
I could check for NODE_ENV in the backend and not send an email, but I'd like access to the email contents in my playwright test, but without actually sending an email.
See, there are still awesome sites on the Internet. Here you can test-drive roughly 100 monospaced programming fonts. https://www.programmingfonts.org/
I don't have time to look through all of them, so let me know what your favorites are. #webdev
It's always so frustrating when all the web accessibility content only talks about text heavy websites and forms. Like yes, I get it, I should have alt text on images. But there's so little information about how to build accessible web apps. What do I do if 80% of my page is a WebGL canvas and the other 20% is all buttons/sliders? How do I structure this if there is basically no "regular text" on the entire page?
Dites, développeuses z'et développeurs, régulièrement, dans mon cercle professionnel direct, j'entends dire que vous n'aimez pas #CSS (voire #HTML).
Question sérieuse et qui n'appelle pas à réveiller quelconque troll ou débat sans fin : pourquoi n'aimez-vous pas ce langage ?
Qu'est-ce qui vous chiffonne, vous rebute ?
D'où vient votre éventuel manque d'intérêt ?
J'ai déjà des éléments de réponse proches de moi, mais je suis curieux d'élargir la question ici.
Once I thought, what if there was a CSS file that makes the document look like it is a command line interface... So I made one, but I really don't know what it could be used for :) #webdev#css
Should I use ::after pseudo-element to add a sort order indicator?
It feels like it's not very accessible because the semantic HTML content doesn't actual contain the sort indicator... but the way I'm conditionally adding it is by reading the aria-sort attribute so maybe that's the accessible part of things and the ::after content doesn't need to be SR-friendly 🤷
Your boss, manager or client will never ask you to take time to refactor your code. They'll never ask you to set up a test suite for the code you wrote. They'll never ask you to upgrade your framework.
Do these things every day. Make them a part of your process. You don't need permission.
Django 5.1 alpha 1 is now available. It represents the first stage in the 5.1 release cycle and is an opportunity for you to try out the changes coming in Django 5.1.
This alpha milestone marks the feature freeze. The current release schedulecalls for a beta release in about a month and a release candidate about a month from then. We'll only be able to keep this schedule if we get early and often testing from the community. Updates on the release schedule are available on the Django forum.
As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the alpha package from our downloads page or on PyPI.
The PGP key ID used for this release is Natalia Bidart: 2EE82A8D9470983E.