You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the one hand, module IDs are UUIDs and really are not human readable. The only way filtering by module ID is any use is if the person who's doing the filtering is aware of the module IDs to begin with.
On the other hand, this would be a (kind of, potentially) destructive change since we'd technically be removing functionality.
The text was updated successfully, but these errors were encountered:
The only reason to actually REMOVE the functionality is to reduce confusion, like when a user types "a" when searching and a bunch of modules that have an "a" in the ID but NOT in the name show up unexpectedly. I don't think that this confusion is a big deal, since most users will probably type at least three or four characters in a search and the odds of this showing up in most practical cases is small.
Another potential solution is show the IDs either during the search or more permanently. I would personally prefer that users never have to see or deal with IDs, but they are positively EVERYWHERE in Obojobo, and would take a lot of design work to completely remove.
Whatever course we end up going, we'll just need to make sure that the Public Page matches. It currently says you can add a module by searching by name and ID, and even provides the ID for whatever module you're looking at.
On the one hand, module IDs are UUIDs and really are not human readable. The only way filtering by module ID is any use is if the person who's doing the filtering is aware of the module IDs to begin with.
On the other hand, this would be a (kind of, potentially) destructive change since we'd technically be removing functionality.
The text was updated successfully, but these errors were encountered: