TypeError: any is not a recognized Joi type about joi-to-swagger

[MarkHerhold]

A second thought: Joi allows users to provide new types via Joi.extend(), so I see the potential for a lot of users to run into this same type of issue. Perhaps another approach would to allow users to provide "type resolvers" (think plugin) to j2s that way we push undefined behavior down to the user level. Thoughts?

[Twipped]

Swagger only allows for one data type per property, so support for joi.any() wasn't implementable. I'm not actually sure swagger has a way to define a forbidden property, short of omitting it and adding additionalProperties: false to the object definition.

If you can provide an example swagger output that would fit that that schema, then I can look into adding it.

[MarkHerhold]

Good point about swagger output, but I think that throwing an unrecoverable error is probably not the best way to handle this as one field ruins the bunch.

My initial thought is that any could be represented as binary or any types could be left out/suppressed by default.

Would you accept a PR to suppress the any type from showing up in the schema and not throw an error (perhaps log a warning)?

[Twipped]

The plugin idea makes the most sense to me. I'll mull it over and see if I can come up with an api I like.

I would accept a PR to ignore any and not trigger an error, you can probably do it by just adding any: () => false to the parseAsType collection. It definitely should at least issue a warning (maybe via util.deprecate) if it's going to ignore the entry. Otherwise people wouldn't understand (and possibly not even notice) why it's absent.

[Makpoc]

Sorry for the sort-of-necro-bump, but didn't want to open separate issue about topic, discussed here.

I looked around but didn't see any PRs related to the Joi.extend() issue, mentioned above. Was any progress made on that?

[Twipped]

Not really. The way I've addressed it in my own projects is to just explicitly define the swagger using the meta() override.