In the test, since `@nouser1` isn't a user the new assertion isn't a very strong one. Better to test with `t...@admin1.com` I think. Besides that I think this will be good to merge to handle the server-side parsing.
Note my comment above about the behavior when typing in the editor too. That is really a separate issue but similar. Not too critical, so can be dealt with later if you wish. --- ** [tickets:#8299] More precise markdown @username regex** **Status:** open **Milestone:** unreleased **Labels:** gsoc19 **Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema **Last Updated:** Mon Jun 24, 2019 04:27 PM UTC **Owner:** nobody If there exists a user with username "foo" and some markdown content has john...@foo.com then we'll incorrectly get a username link of @foo in the middle of that email address. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
