Rodrigo
Rodrigo
@IamBlueSlime Thanks a bunch for doing this, our priority is getting v8 PR first and then this should be our next step
> I'm not interested right now in switching away from Yarn 1 and over to NPM so we should revert the package-lock.json and changes to the CI scripts. > >...
@IamBlueSlime Can we merge the latest changes, i think we should start considering having Nx asap, there are some stuff that we have pending that can actually leverage having this...
> > @IamBlueSlime Can we merge the latest changes, i think we should start considering having Nx asap, there are some stuff that we have pending that can actually leverage...
@IamBlueSlime I've noticed that the Nx PR has been merged, any news so far if it is included in any of the latest versions?
@IamBlueSlime Do you have any plans on having this? I believe we were close to merge this experience
@bmcgoncalves So what you are looking for is to use class-validator and provide custom errors right? You can do that easily by creating a simple interceptor that uses class-validator and...
@bmcgoncalves I have discussed that idea but it would imply having a custom payload, i might have to talk with @WonderPanda and open a suggestion for the whole community that...
I will delay this until we have Nx, there's the following integration (https://www.npmjs.com/package/@nx-plus/docusaurus) that would be worth looking at
@vincent-benbria Is there a way to proxy the old disconnect event, I'm trying to think of a way to bring compatibility to pre-existing code. If not, if we decide that...