APIs and Microservices project submission system - feedback/suggestion

I don’t know if this was discussed before, and if yes please redirect me to that thread and close this one if it’s a clone, because I haven’t yet found one.

I like how responsive the assessment system is, and repl is working flawlessly so far.

However I think it’s pretty repetitive that I have to copy and paste the same link in every challenge (of the same module).

So here’s what I have in mind: How about us submitting only one link for the whole module, or the assessment system somehow remembers the last link we pasted so we don’t need to paste it anymore.

I hope that explains what I think. I’m open to discuss about this matter.
Again, thank you for the lessons, I’m in love with them.

Hello there,

I cannot remember if this has been discussed anywhere specific. So, we can have some of it here :+1:

As it stands, the submission inputs should remember previous inputs, the same way most inputs do - browser cache. So, I have used the suggestions which pop up, when you focus on the input:

Ignore why such random links are there - I have been doing a lot of testing for this side of the platform

Unless I am misunderstanding, this would be more annoying than helpful. Often, campers submit different links (new project started, or moved project from Repl.it to Glitch, or CodeSandbox, or miscellaneous hosting) throughout the curriculum.

Otherwise, it might be beneficial if you expand with more user stories which could be implemented for this feature?

  1. Thank you for the suggestions, that could be a workaround and it would work for some. I don’t do that personally but I have a sorta better one for me. I’m working on 2 machines at the same time so I submit on one machine using 1 single thing: Ctrl+V, because I don’t do anything else in that machine except testing, so the latest copied link still remains intact in clipboard.
  2. However, from a user experience standpoint, an extra step is an extra step (it bugs me because I come from human-computer interaction program so this is an important thing during UI design for me).
  3. The link submission is very useful for those who might want to change/fork/move projects like you did. But I’m not very sure about that situation in my case and please correct me if I’m wrong about this: As far as I’m concerned while I am doing (and I’m still doing) the challenges in the APIs section, there are 4 smaller modules (npm with 10 challenges, node/express with 12, mongodb with 12 and last projects with 5). The last module might actually need flexible link submission, but for the first three, I believe we submit the exact same link (be it glitch, repl, or even github) for each small module, which is 9 extra steps in first one, 11 in the second and 11 in the third.
    What I’m trying to suggest is for each of these first 3, we could have a unique section, probably at the top left/right where users submit one single link that works for the whole process, and then when they finish each challenge, all they have to do is clicking the Submit/Check button.

That is one of the solutions, while the latter that I mentioned was having a smart bot, which could be troublesome as you pointed out. Would be interesting to have resource to test these features out.

I’m just talking from user experience stand point. Features might be difficult to implement due to project structures but it would be very nice to have them. And I hope that makes my statements clearer to you.

From here, I recommend you open a feature request issue on the main repo: freeCodeCamp/freeCodeCamp: freeCodeCamp.org’s open source codebase and curriculum. Learn to code at home. (github.com)

As it stands, I imagine we are still hoping to limit the amount of information stored, and passed, in the servers (database). So, a specific implementation would be to store the most recently submitted link in the local storage, and pre-populating each field with any available/relevant link.

1 Like

Thank you for the link, I did not know of this before. I’ll submit a request on the main repo soon.
Your suggestion is exactly what I was about to say, which is using browser cache to save personal relevant data (provided users allow using cache in the first place). That would be very handy.