azjezz.bsky.social
Rust Engineer @Quizlet, Previously @Bumble, @CoopTilleuls, and @Symfony.
39AC CCA4 FD30 0D04 C840 6EB3 B00E 0A46 B3F1 C157
he/him
86 posts
332 followers
181 following
Prolific Poster
Conversation Starter
comment in response to
post
Quick hotfix release! Mago v0.13.1 is out! 🐛
github.com/carthage-sof...
comment in response to
post
PR for those interested :)
github.com/carthage-sof...
comment in response to
post
I think it's a choice, i personally find smaller code units easier to deal with. I wouldn't say it's a *MUST* or not doing it is bad
comment in response to
post
I DONT UNDERSTAND THIS JAVASCRIPT STUFF, I NEED MY LLM
comment in response to
post
personally i prefer that, if i have more than ~6 args, I will make a struct for it, i don't mind the "complexity" as long as it makes the code easier to understand and reason about it.
comment in response to
post
wouldn't be simpler to split the the closure into its own function?
comment in response to
post
If you find Mago useful and want to support my work, consider sponsoring me!
Your sponsorship helps me dedicate more time to building better PHP tooling—faster linting, smarter formatting, and more powerful static analysis.
👉 github.com/sponsors/azj...
comment in response to
post
why not use FFI? 🤔 Its propably easier for people to enable FFI than to install a custom extension.
comment in response to
post
Already using it on bigger projects 😅
comment in response to
post
Was asking for usage feedback, simply install mago and use it on your PHP project :D
There's an installation guide here: mago.carthage.software
comment in response to
post
Someone might potentially do want it to fail 🤷♂️ hence why the fix for it requires the -p flag.
But as we are planning to add an LSP in the future, the code will be highlighted in the editor before even running the test.
comment in response to
post
would love to hear your feedback on this :)
github.com/carthage-sof...
You can use the following configuration: gist.github.com/azjezz/04d7a...
and run `mago fix -p` to remove all those assertations.
comment in response to
post
examples: github.com/carthage-sof...
hopefully soon we will generate documentation from those examples.
but you can do `mago lint --explain php-unit/redundant-instance-of` for now :)
comment in response to
post
will release in few minutes :)
github.com/carthage-sof...
comment in response to
post
Bonus: Mago can detect aliases, so even if the RHS is new Foo() while LHS is Bar::class, it will report it if they are the same class :)
comment in response to
post
Can i steal this idea and add it as a linter rule to Mago? 👀
comment in response to
post
The speed-up came from changing nothing in the formatter itself! I discovered that external files were mistakenly loaded in the source manager, even though they’re never formatted. Fixing that saved most of the time spent in `mago fmt`. 😅
comment in response to
post
Install it easily:
```
curl -sSf carthage.software/mago.sh | bash
```
Already on v0.0.13? Update in seconds:
```
mago self-update
```
comment in response to
post
Mago 0.0.11 is out! 💨
This quick release addresses a couple of bugs:
* Improved error handling for unterminated multiline comments
* Fixed formatting issues with literal strings
github.com/carthage-sof...