Nathan

Results 11 comments of Nathan

There's a mismatch in the path API. We are using Node v6.16.0 in production, but it doesn't support the new path API. I have to apply this diff before packaging...

Yeah, it is very large. We have microservices for different parts of the schema. I do a `yaml.safeLoad(file)` for them all before sending them to `initialize.externalSchemas`. Reading the yaml files...

This is all done loading yaml files and programmatically generating the path operations. Loading and generating all of that only takes 4 seconds or so.

I'm sending the paths to initialize as: ``` [ { path, module: { get: Function() } } ] ```

Using this: ``` console.log(new Date().toTimeString()); openapi.initialize({ apiDoc: this.apiDoc, app, enableObjectCoercion: true, externalSchemas: this.externalSchemas, paths: this.paths, promiseMode: true, validateApiDoc: true }); console.log(new Date().toTimeString()); ``` Gives this: ``` 18:57:13 GMT-0600 (Central Standard...

Yeah it's about the same locally. ``` ticks parent name 2573 9.4% v8::internal::JsonStringifier::SerializeString(v8::internal::Handle) 2573 100.0% v8::internal::Builtin_JsonStringify(int, v8::internal::Object**, v8::internal::Isolate*) 2561 99.5% LazyCompile: *stringify ./node_modules/fast-json-stable-stringify/index.js:19:32 2554 99.7% LazyCompile: *stringify ./node_modules/fast-json-stable-stringify/index.js:19:32 2509 98.2%...

I hacked around it by traversing the schema/extensions and load only the ones i need. However, the constant encode and decode to JSON could be fixed and most of the...

Been almost a year and this PR still hasn't made it in. What gives?

Would be willing to help out if y'all need it. I'm a senior dev and have been using React/Typescript for 6+ years. I love YTMD and use it daily.

SuperSlicer has this and it's a fork of PrusaSlicer. The ticket is over a year old. Would be really nice for calibration tests.