Erik C. Forés
Erik C. Forés
Profanity::blocker("message")->dictionary($dictionary)->filter()
I already told you the structure... ``` [ { "language": "en", "word": "bitch" }, { "language": "en", "word": "fuck" } ] ``` Anyway, the best way to do it if...
Older versions and future versions were removed due a trademark notice that I received. Older versions are lost unfortunately
> This appears to have been broken in `11.0.11`. Last version that doesn't suffer from this issue is `11.0.10`. Correct. Just checked!
> Does anyone have a workaround for this? It breaks for us too Fix it to 11.0.10
I have found out that `chi.URLParam` does not work and `request.PathValue` does...
Oh yes, it's pure type gimmicks, there's no new logic involved.
In our case, we have a shared standards package where we export common base configurations for stuff like `eslint`, `prettier`, `tsconfig` among others. I wanted to add the `oxlint` config...