Discourse reference detection bug, users case-sensitive #1479
Labels
bug
Something isn't working
Comments
|
As a workaround, I've tried including a lowercase alias in the identities settings. {
"username": "Beanow",
"aliases": ["github/Beanow", "discourse/Beanow", "discourse/beanow"]
},This fixes the mentions for me :] Perhaps as part of the unified reference detection we can discuss some canonicalization methods. |
|
Good catch @Beanow. And good find with the workaround. |
Beanow
added a commit
that referenced
this issue
Jan 7, 2020
Gets the username of a user, if it exists. Helpful for fixing capitalization issues such as #1479, and verifying the user exists for reference detection.
This was referenced Jan 7, 2020
Beanow
added a commit
that referenced
this issue
Jan 7, 2020
Gets the username of a user, if it exists. Helpful for fixing capitalization issues such as #1479, and verifying the user exists for reference detection.
Beanow
added a commit
that referenced
this issue
Jan 11, 2020
Discourse ReferenceDetector detector that relies on database lookups. (Should be the main way to solve #1479, when UniRef is used by all plugins)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Noticed this as I was working on some prototype reference detection for Initiatives.
In the current implementation an
@Beanowmention on the forum creates the URL https://discourse.sourcecred.io/u/beanow. When parsing this URL the username looks likebeanow, creating an edge towards the lowercased node address. Which will be a dangling edge as my actual user node is capitalized.┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: