Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

Errors and Warnings from the DesignTimeHost shouldn't be strings #275

Closed
Alxandr opened this issue Jun 1, 2014 · 4 comments
Closed

Errors and Warnings from the DesignTimeHost shouldn't be strings #275

Alxandr opened this issue Jun 1, 2014 · 4 comments

Comments

@Alxandr
Copy link
Contributor

Alxandr commented Jun 1, 2014

Currently, the design time host gives diagnostic messages as strings (that VS and other consumers then have to parse). These strings obviously are generated from an object containing sources-file, line-number etc. and transforming that into a string, just to have the receiver parse it again seems kind of impractical. Shouldn't rather a representation of the raw object containing all the metadata be transferred, and then if a consumer needs it as a string it can generate it itself?

@glennc
Copy link
Member

glennc commented Oct 1, 2014

We recommend parsing the string, and that's what VS uses. But if you want this behavior then we could look at a pull request. Are you still interested in the change?

@Alxandr
Copy link
Contributor Author

Alxandr commented Oct 1, 2014

Yes. I still want this change. Parsing the error string is not pretty. I can look at implementing this and pull requesting it in a few days when I have time.

@glennc glennc added this to the Backlog milestone Feb 12, 2015
@glennc
Copy link
Member

glennc commented Feb 12, 2015

@Alxandr leaving this in the backlog for when you get to it.

@troydai troydai modified the milestones: 1.0.0-beta4, Backlog Mar 24, 2015
@troydai
Copy link
Contributor

troydai commented Mar 24, 2015

Addressed in ac2f433

@troydai troydai closed this as completed Mar 24, 2015
@troydai troydai self-assigned this Mar 24, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants