You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having this module explicitly depend on Q is an inconvenience when user doesn't want to use Q. The browser version also packs a copy of Q, even if we don't want to use Promise or want to use another Promise polyfill.
Would you consider removing explicit dependence on any specific Promise implementation, and allow user to supply a polyfill?
Some ideas:
expose a swaggerClient.Promise that user can set but assign global Promise to it by default.
If Promise is not defined, then throw error if usePromise is true.
Having this module explicitly depend on Q is an inconvenience when user doesn't want to use Q. The browser version also packs a copy of Q, even if we don't want to use Promise or want to use another Promise polyfill.
Would you consider removing explicit dependence on any specific Promise implementation, and allow user to supply a polyfill?
Some ideas:
swaggerClient.Promise
that user can set but assign global Promise to it by default.Q.defer can be implemented using the ES6 Promise:
This change would require a major version bump.
The text was updated successfully, but these errors were encountered: