Apache Allura™

If you add a new file that you wrote (is show-hint.css?) you should add the Apache License header like our other files have.

If you add a new file that is from elsewhere like show-hint.js you need to include the license details at the top of the file, like you've done. It must be a compatible license (MIT is) https://www.apache.org/legal/resolved#category-a Also add it to LICENSE and Allura/LICENSE following the pattern used in those files. And add it to rat-excludes.txt alphabetically. That file is used for for our licensing check, so we indicate that its ok that it doesn't have the Apache License header.

What is keyCode == 50? a comment would be nice there. I figured out it means shift + 2 aka @. What about other keyboard layouts? Possible to check for @ more directly?

If there is only one user on a project, pressing @ completes their name automatically. I guess that's ok if its the only option, but a little surprising.

I like how it shows the user's full name and username. Is it possible to have it match on full name too? So I could type @ and then their full name and it would select that user? Right now it only works to match on their username. Not a big deal though.

Nice that you are able to disable it within code sections.

In the helper, some of that code dealing with words & lines & lists is pretty dense and not obvious to me what it's doing. Do you mind adding a few comments? Not every line, but a few would help to explain what its accomplishing.

Might look nicer not as monospace.

suggestion for followup work: might be good to also suggest names for anyone who has commented in the thread, and the creator (of the ticket for example, but consider other artifact types too)

another followup idea: might be nice to style @foo in the editor, like links are blue and underline. Just a visual helper, not an actual link unless you click preview. However this might be quite hard or not practical, as it would rely on the codemirror markdown parsing to tokenize @foo so it has a span & class of its own.

This is exciting!

Hi.. Dave

I have updated licensing information, added some comment lines for better clarification into the user mentions helper and also improved regex. Please advice with above reply too

Thanks

Hi,

Licensing is looking good.

KeyboardEvent.key == "@" is much clearer to me. If it is well-supported, I think its definitely better.

Autocomplete on a single entry I think could be confusing when the project only has 1 admin (which many could). In that case, as soon as you type @ it expands to @someusername and you might have been wanting to type somethign completely different like @2pm. So I think the autocomplete dropdown would be nice to use still, so users can choose to autocomplete or not. It looks like the addon has a completeSingle setting which might handle this.

For matching a full name, if there is a user with full name "John Doe" and username "john", then typing @ followed by Doe does not match his entry. I don't think this is a dealbreaker, but would be nice. Could be followup.

For all the followup I suggested, yes, I meant that it could be done later. If you agree they make sense, you or I could make tickets for them and then you can go back to them as time allows. Some will be easier or harder, etc, so no need for them to be worked on right now. (I think supporting other usernames that are involved on the current thread, besides admin, would be most valuable - but still doesn't need to happen now).

Hi..

Nice. I did following modifications in source

• KeyboardEvent.key == "@" is added instead keycode
• completeSingle option is used to display list for one item
• Text maching is set to case insensitive So "john" will match "John Doe"

Yeah good idea to make tickets for follow up works. So we can remember the Todo follow up tasks.

Thanks

I was doing some cross-browser testing and noticed in Edge that the keypress wasn't being detected. So I changed the check to handle both forms:

if(event.key === "@" || (event.shiftKey && event.keyCode === 50 /* "2" key */)) {