[allura:tickets] #8299 More precise markdown @username regex

- **status**: review --> closed - **assigned_to**: Shalitha Suranga - **Reviewer**: Dave Brondsema - **Comment**: Nice, works better now :) --- ** [tickets:#8299] More precise markdown @username regex** **Status:** closed **Milestone:** unreleased **Labels:** gsoc19 **Created:** Thu Jun 06,

[allura:tickets] #8299 More precise markdown @username regex

- **status**: in-progress --> review --- ** [tickets:#8299] More precise markdown @username regex** **Status:** review **Milestone:** unreleased **Labels:** gsoc19 **Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema **Last Updated:** Mon Jul 01, 2019 05:31 PM UTC **Owner:** nobody

[allura:tickets] #8299 More precise markdown @username regex

Hi.. I have updated autocomplete regex in ss/8299 Thanks --- ** [tickets:#8299] More precise markdown @username regex** **Status:** in-progress **Milestone:** unreleased **Labels:** gsoc19 **Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema **Last Updated:** Mon Jul 01, 2019 05:06

[allura:tickets] #8299 More precise markdown @username regex

- **status**: open --> in-progress --- ** [tickets:#8299] More precise markdown @username regex** **Status:** in-progress **Milestone:** unreleased **Labels:** gsoc19 **Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema **Last Updated:** Wed Jun 26, 2019 08:19 PM UTC **Owner:**

[allura:tickets] #8299 More precise markdown @username regex

Merged ss/8299 --- ** [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:** Wed Jun 26, 2019 04:28 PM UTC **Owner:** nobody If there exists a user

[allura:tickets] #8299 More precise markdown @username regex

Hi.. acutually I missed to replace `nouser` with correct one. Now I updated the branch. Yeah we can keep this ticket open until I fix the editor typing improvement. Thanks --- ** [tickets:#8299] More precise markdown @username regex** **Status:** open **Milestone:** unreleased **Labels:**

[allura:tickets] #8299 More precise markdown @username regex

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

[allura:tickets] #8299 More precise markdown @username regex

Hi.. @brondsem I made branch `ss/8299` and improved regex by adding `\B`. So it will not catch things like `john...@foo.com` and `johndoe@foo`. --- ** [tickets:#8299] More precise markdown @username regex** **Status:** open **Milestone:** unreleased **Labels:** gsoc19 **Created:** Thu Jun

[allura:tickets] #8299 More precise markdown @username regex

There's also weird regex matching behavior when typing in the editor. `@foo.` will trigger the autocomplete again when you type the `.` It also happens with other punctuation like `@foo=`. And can happen at the beginning like `@//.?` --- ** [tickets:#8299] More precise markdown @username

[allura:tickets] #8299 More precise markdown @username regex

--- ** [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:** Thu Jun 06, 2019 04:31 PM UTC **Owner:** nobody If there exists a user with username