-
Notifications
You must be signed in to change notification settings - Fork 142
V0.5.0 - Enable platform extensibility in ManifoldJS #206
Conversation
…ENSE.txt, package.json, README.md
…ndencies as well as then main module and to support both promises and callbacks
…dateManifest from loader module
…name--it's now determined by downloading the package.json from the specified source
…t present in the project
var deferred = Q.defer(); | ||
getW3cManifest(siteUrl, program.manifest, function (err, manifestInfo) { | ||
if (err) { | ||
return deferred.reject(err); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be great in 6.0 to move to standard promises, or is there some advantage to using Q?.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking the time to provide all this feedback. There was no time to include more changes for the current release, but we will take this into consideration for the next update.
This release involved significant re-architecture in a limited time and there are a number of things that had to be postponed. Regarding the use of standard promises, this is something that we considered and need to investigate.
V0.5.0 - Enable platform extensibility in ManifoldJS
Enable platform extensibility in ManifoldJS and allow users to implement additional platforms that can be added to the tool (Closes #205)