[Bug]: Update error messages

[chiefmikey]

Bug

Currently User Not Found is the only error message.

Fix

Add unique messages depending on the actual failure.
More descriptive or instructive but still "front end friendly" aka an average user should understand what's happening.

Potential errors to test + respond to:

• Server timeout
• Server cors error
• Server not found
• Server API limit ([Bug]: Fix API limits #92)
• No user
• No repo

Open to suggestions of anything that might be useful or informative for the user.

[Akidane47]

May I have this dance?

[chiefmikey]

@Akidane47 Yes please :) I wasn't expecting anyone to even see these issues so give me a bit to refactor a few things so contributing is more straightforward. I'll assign you when ready, hopefully in the next day or two. Thanks!!

[chiefmikey]

It's ready for you @Akidane47, reach out here if you need anything. Thanks!

[Akidane47]

My first thought is having two separate search bars or buttons for searching users and repos? I'm noticing it's having a harder time searching or finding repos than it is with users and it could make the error handling much easier. Style wise I'm not sure how you would want that to look if that's a viable solution. If not, I can just start adding middleware to handle different exceptions and errors

[chiefmikey]

I'd like to keep it as a single search input + single button, that may change in the future as #101 and #103 are implemented but ideally it will keep leveraging delimiters in a way that is compatible with url destructuring so that the input chiefmikey/gitlang results in the path https://gitlang.net/chiefmikey/gitlang and vice versa.

Do you have any examples of repo searches that are giving you issues? Ultimately searching a repo should be easier since it's the same function as searching a user but instead of listing and compiling languages for all of the user's repos it's just pulling results for the one specified repo in search. So if you're seeing anything off with that there may be a bug to look into.

For the error messages, it's probably easiest to implement responses directly in the routes for repos, languages and the auth, then flow the error handling to send the custom message to the front end.

Example (variable names aren't accurate, just descriptions):
Input: chiefmikey/repo-doesnt-exist
Catch error in languages: if error = no repo => { error: ${repo}: Not Found }
Assign in front end submit method: error = allData.error
Condition in front end html: #if error <h4>{error}</h4>

In prod this is a serverless front end but if you want to use a middleware solution you can test it in your branch on the local server and after approval open a PR on the auth-server headless api to add it.

Thanks in general too for your ideas, it's really helping me think about the current implementation and what info needs to be documented!