-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to export library as webgmex #333
base: master
Are you sure you want to change the base?
Conversation
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.
I like it in general, and if there is no change required in regards my comments, I can live with that :).
.then(function (rawJson) { | ||
if (parameters.libraryName) { | ||
// We need to adjust this when the exportee was a library. | ||
delete rawJson.kind; // This is lost at this point. |
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.
i believe i know where this come from, but is this really the good behavior?
shouldn't we enhance the library info with the kind to begin with?
.finally(restoreProcessFunctions) | ||
.nodeify(done); | ||
}); | ||
|
||
it('should fail to exportProjectToFile when branchName does not exist.', function (done) { | ||
var worker = getSimpleWorker(); | ||
|
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.
any chance to add a test that would use the exported libary and run some traversal to see if everything goes well during the read of the nodes?
No description provided.