Dmytro Shchehlov

> Import/export (common.js and esm modules) are actually far from clean architecture, because you need to know certain places where other modules located it is not correct. To import some...

Hey, @jonathon-m Interesting idea. But I suggest don't do it in so direct way. The first reason is that your api can have a several consumers some of them could...

@jonathon-m I'm going to add required functionality with some "post-processing" utilities. ```js const { Schema } = require('mongoose-schema-jsonschema')(require('mongoose')); const { postProcess } = require('mongoose-schema-jsonschema/post-process'); const BookSchema = new Schema({ title:...

@maritter , hi, Thanks for the issue. I considered such behavior on early stages and decided to remove "required" from the model, when using "selection". The motivation is: - when...

@maritter Hi, yes, I have an idea. But you don't like it ... You have different (at least) three different messages in you API: - `CreateBookInput` - `Book` - `PatchBookInput`...

@vemundeldegard , yes, it is still maintained. Actually I'm not sure that code is ready to be covered with types. So, I'll be appreciate for PR with type definitions )

Hi, I will add support for `strict`-option of mongoose-schema (https://mongoosejs.com/docs/guide.html#strict) In case when `strict` equals `"throw"` the json schema will get `additionalProperties: false` (the same behavior will be repeated for...

Fixed in v1.3.0

@irvingv8 , actually it makes sense. So, if `required` is a function let's treat it as optional. What do you think?

Oh! ) @Serg046 greate idea ... But, what if some service have dependency like: `IInfoLogger & IWarnLogger`? We need to know all combinationes ...