Open Jesn opened 5 years ago
@Jesn could you provide some more details about this issue? This isn’t extremely helpful in its current state. Could you describe what the bug you are encountering is please.
I just noticed this problem as well. It seems like it has to do with specifying a parameter as a type string with a format of uuid. Viewing other examples with no parameter and bodies or responses with uuids seem to work just fine. When opening a route with a parameter though, it outputs the warning Could not find component JsonSchema_string_uuid
. I'm not sure if it's just a display thing though, as it seems to still validate the input as needing to be a uuid.
Can't copy/paste the stack (different system not on the internet), but it comes from index.js:19
, root-injects.jsx:112
, memoize.js:62
, json-schema-components.jsx:53
in version 3.23.1.
Can you provide a sample to reproduce the issue?
The "Could not find component" warning itself is harmless in this context, we'll probably want to silence that in the core since it's causing confusion.
isEventSupported.js:18 Could not find component JsonSchema_string_uuid t @ isEventSupported.js:18