Michael Braun

Or for the lazy `ExplicitBooleanOptionHandler` is also a way to go. Simply add `handler = ExplicitBooleanOptionHandler.class` to your `@Option` annotation.

Running into the same problem here. I tried the suggestions above with `react-data-grid@react-data-grid`, but no luck there. Had to roll back to `[email protected]` for the time being. ```javascript module.exports =...

Just tried your recommendation, but no avail. both `path.resolve` and `require.resolve` resulted in the same path. ``` { path: 'C:\\Data\\Development\\someproject\\node_modules\\react\\jsx-runtime.js', require: 'C:\\Data\\Development\\someproject\\node_modules\\react\\jsx-runtime.js' } ``` The only thing of note I...

> Does the `jsx-runtime.js` file actually exist at that path? 🤔 I checked just now and yes, it does.

> Might not be an issue with webpack then, might be node failing to import as it respects its esm import semantics. > [facebook/react#20235 (comment)](https://github.com/facebook/react/issues/20235#issuecomment-728405448) > > Best bet would...

Running into a similar issue, where nested objects can't be designated as a filterable field, otherwise the system will throw an error: `CannotDetermineInputTypeError: Cannot determine a GraphQL input type for...

@lukasender Sadly no, ended up designing my structure differently to avoid having to use this setup all together.

Any specific implementation or is this gonna be a generic implementation so you can hook up generic data parser? (Thinking about stuff like logstash)

YES!

> the usage of macros is configuration files I'm guessing it's supposed to be `in` :shipit: