Skip to content

Making xmlError js friendly.#5

Open
gotama wants to merge 5 commits intocdegalitt:masterfrom
gotama:forked_merged
Open

Making xmlError js friendly.#5
gotama wants to merge 5 commits intocdegalitt:masterfrom
gotama:forked_merged

Conversation

@gotama
Copy link
Copy Markdown

@gotama gotama commented Oct 29, 2020

With regards to #2

Comment thread src/xml_errors.cc

Local<Value> err =
Exception::Error(Nan::New<String>(error->message).ToLocalChecked());
Local<Object> out = Local<Object>::Cast(err);
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason I removed this, because casting err to the out object is the reason the formatting for JS broke.

A stack trace doesn't fit nicely into a key value JS object. Im trying to think of a more elegant way to append a stack trace. Will update if I come up with anything.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also error->message might not be a stack trace, as im using that as xsd validation error messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant