express-restify-mongoose
express-restify-mongoose copied to clipboard
Convert to TypeScript
- [x] Type check in CI
- [x] Build ESM + CJS
- [x] Build .d.ts
- [x] Run tests on build output
- [x] Add entrypoints in package.json
- [x] Also bring moredots back in here
Breaking changes
allowRegexnow defaults tofalseand returns an error when the query includes$regexoptions.accesscan now be anasyncfunction (or return aPromise) and no longer accepts a callback- Removed
defaultsmethod: apps should define default options and spread them intoserveoptions
Notable changes
- Build output is ESM first but CJS is also present. In practice, this should be transparent.
The "code smells" are bogus, I'm tempted to remove this workflow 🤔
@florianholzapfel Are you open to disabling SonarCloud? I feel like it's not helpful since it seems like the only reason it started failing (in test files of all things!) is because formatting is now consistent, which enabled it to detect "duplication" that is neither new nor unexpected.
Do note that I've added a more exhaustive ESLint configuration so we do have some level of static analysis, along with TypeScript. Of course they are different tools but the general idea of improving code quality is the same.
@florianholzapfel Are you open to disabling SonarCloud? I feel like it's not helpful since it seems like the only reason it started failing (in test files of all things!) is because formatting is now consistent, which enabled it to detect "duplication" that is neither new nor unexpected.
Do note that I've added a more exhaustive ESLint configuration so we do have some level of static analysis, along with TypeScript. Of course they are different tools but the general idea of improving code quality is the same.
Hello @Zertz, if SonarCloud gets into your way, feel free to disable it. I was just playing around with it when I thought I could spend some time working on the project.
As a side note, I really appreciate the great work you are doing here!
I removed the workflow but it seems like there's probably an app/integration configured in the repository's settings which I don't have access to.
Thanks, I've been wanting to put some time into this for a while!
@Zertz @florianholzapfel Any updates on this PR? There are some things I'd like to work on like the updateDeep option, but since this PR seems to be the future of this repository, I'm waiting for it to get merged.
Let’s give Florian another week or so and then I’ll merge.
@Zertz @florianholzapfel Can we get this merged now? :)
I set a reminder to merge this and publish a major version.
@T-vK v8.0.0 is published on npm, create an issue if you run into problems 🙏
@Zertz Thank you so much! :pray: