Michael Brevard

The issue with this is as follows: The ID attribute is primarily used for in-page navigation. It also generally shouldn't be non-standard, as the ideal is a selector that is...

> However it would still be nice to modify our regex, would it be extremely difficult ? This would depend, I'd have to look into it, because it can be...

If it turns out to be too resource-intesive to the point where it causes noticeable slowdown, I believe we should really think whether or not this is necessary. If someone...

> But the issue I'm seeing here is that _we_ are the ones injecting the quotes that break the original HTML True, but then again, that's just in a scenario...

> only possible scenario I can think of is an image of HTML code, so its `alt` would contain HTML content to cater to screenreader users Considering you can also...

Hey! I sincerely apologize for the amount of time it took me to come up with a solution to this. Right about the time I made the previous iteration, I've...

On second thought, this should probably be reworked to include semicolon separated headers, and perhaps create a helper function to determine what to separate by. I'm just worried about the...

Seeing as this is already supported by the underlying [http lib](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/node/http.d.ts#L589) I will keep this a draft until I find out it works fine. If it doesn't I will likely...

TODO: Allow for non-existent messages to go through. If done correctly, could prevent a breaking change. Also yes, I will move the type to /types/, this is not final yet...

@kazupon should this change VueMessageType or should this be added as an overload of t? Curious to hear your opinion on how to proceed with this. Both options have their...