Alec Thomas
Alec Thomas
No, because it doesn't cover the use case of when you want to explore a package. For example, you remember that `encoding/xml` has a function to escape text, but you...
Aaah. I'll take a look.
As discussed in Gitter, I was unable to test this due to an issue with indexing on OSX.
More discussion on Gitter ([February 17, 2017 10:18 AM](https://gitter.im/DamnWidget/anaconda?at=58a6335821d548df2c1caedf))
That would be ideal in my mind.
Further discussion in Gitter ([February 17, 2017 10:31 AM](https://gitter.im/DamnWidget/anaconda?at=58a6365e1465c46a5675bb5b)).
Sorry, yeah, I am referring to reconstructing a URL from a Route. Equivalent to Flask's `url_for(endpoint, **values)`. FWIW, I don't use any complex features of Werkzeug's routing at all, so...
Yeah, in Flask I have always been rigorous about using IDs everywhere and using those in url_for. It works well, but you do have to be a bit more disciplined.
I can't reproduce this, but it might be a bug in an older version of Chroma. I've tagged v0.7.1 if you want to update.
Those changes are small enough that they could just be manually applied to the XML lexer I think.