generator

...this boilerplate is awesome, thank you for sharing it guys 👍

Bug Report Checklist

• [~] Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator, yes I used the validate function of the api generator
• [5.0.0 ] What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?

Currently, few icons are not visible in dark theme. Make them visible by using theme neutral icons. May be we can make use of https://shields.io/ to generate our own kind of badges. For eg: Javascript.

Search Terms

native ecmascript, esm, plugin

Problem

It would be nice to write TypeDoc plugins as ESM modules, using node's new native ESM support

Suggested Solution

typedoc can first try to require() the plugin, then if it gets an ERR_REQUIRE_ESM error, it can import() it instead. This will support both CJS and ESM and will also support CJS transpilers like ts-node.

It seem there is an unnecessary call to $this->getImagePath($field->getValue(), $configuredBasePath here.

https://github.com/EasyCorp/EasyAdminBundle/blob/4d22b21d1f0d9160df65135a1b15b5d47ce21f3c/src/Field/Configurator/ImageConfigurator.php#L34-L38

What problem are you facing?

For simple modules the generated documentation contains a lot of sections that simply say "no outputs", "no resources", etc.

Of course it is possible to hide these "empty" sections manually, but if the module changes in the future, you have to explicitly remove it again.

How could terraform-docs help solve your problem?

It would be great if terraform-do