@_smontlouis Dernière fois j'avais du taff, et les enfants à gérer, j'ai bossé via Codex Mobile, et il s'est mis à me balancer des screenshots du boulot tout seul (en voyant que j'étais sur mobile je pense) 😍
Have you ever had your code snippets in your docs drift from your current API's and have it reported by users? 👀
Have you had LLM's hallucinate API's in code snippets in your md examples? 🙄
Today I have the solution you're looking for!
Introducing https://t.co/RXp91IFi2q 🚀
It runs tsc on your .md code snippets and reports any issues it finds using your repos tsconfig with options to autofix, no more outdated or wrong API's in your documentation!
Works anywhere and lints any TS file, comes in three flavors:
- CLI
- VS code extension
- Github action
Highly configurable for any project with sane defaults.
@StevenMadec@_smontlouis J'ai fait ça une fois, depuis il commence tout ses messages par "voici la solution ultime, sans bla bla ni bullshit". Insupportable
Ironically, I think the shift to AI should actually increase 100x the thought and care you put into framework and toolkit selection even if it takes 1/100th of the time to implement.
@_smontlouis Mon plus bel example: Ma datatable de rêve, que je met sur chaque projet Laravel. Vibe codé à 100% une fois, unit testé et SKILL auto-rédigé :
https://t.co/jaVXwIKaOs
Sur chaque projet où je la rajoute, c'est du one-shot systématique. En plus le composant client est en shadcn
I need to understand how git/codex worktrees work.
Any good documentation for someone coming from working on a single branch all the time, and stuck in switching hell?