GET on /queues and /tokens should return sorted by creation time about simplq-backend HOT 9 CLOSED

Sure, go ahead.

from simplq-backend.

Let's discuss over the PR itself. It happens to come sorted, but we need to guarantee it.

Your PR would ensure this happens. For example something in the DB layer might change, and it would be a good to have to ensure this at service layer, or so I thought.

from simplq-backend.

Can I start working on this issue?

from simplq-backend.

Sure. This can be a good task for you after you complete #78

from simplq-backend.

Hi @daltonfury42, looks like this is still up for grabs, I'm looking to get started with #hacktoberfest in a couple of days, mind if I pick this up then if this is still an issue?

from simplq-backend.

Hi @daltonfury42 , just getting set up here - for some reason code traversal isn't working in intellij for me, do you have any tips?
Also, how should the responses be sorted, oldest first or newest first?

from simplq-backend.

Not sure why. It's working at my end. 🤔

You should open simplQ-backend/complete, it should open as a maven project. Try mvn clean package from within intellij... but this shouldn't have to do with code traversal

Oldest first.

from simplq-backend.

Hm ok, i'll see why else traversal could not work.
I tried to simulate the scenario to check the current behaviour and it looks like it already returns oldest first?

Do you have an irc/discord/telegram to discuss further?

from simplq-backend.

Makes sense, especially considering that you're using different database in local and in prod it's good to explicitly ensure consistent behaviour.
I have incorporated your feedback in the PR.

from simplq-backend.