Typescript retozi

[Retozi]

A Typescript implementation without any external dependencies

simply run the server and open index.html in a browser.

or then

    npm install
    npm start

for a dev server

[staltz]

Not working. Check other submissions to see how they work.

[Retozi]

In what sense? I did cross compare and it seems to behave the same way, did it not load at all or did you somehow enter an invalid state with the up and down scrolling?

[Retozi]

I have fixed an issue that leaves you in a semi recoverable state when you get unlucky with the Obi Wans planet, request canceling and scrolling. You might have hit that right when you started testing.

I really cannot find any other difference, I compared it to @tomkis1 solution excessively and I cannot find any difference to it, it behaves exactly the same way except that my solution allows for two scrolldowns.

[staltz]

I got stuck like this. Can't let the UI get stuck.

[Retozi]

Jesus man I suck. Should have seen that... sorry for wasting your time by only testing when clicking up first :)

[staltz]

Some problems still:

• Up and down buttons are swapped around.
• I was able to see a request happen while there was a red match. This didn't happen every time, so I think there is some kind of race condition. But I'm sure there was at least one case where a new slot was filled while there was a red match. This should not occur.

[Retozi]

1. flipped the scroll buttons
2. prevent queries while sith on obi wan planet. This was by design. I took the requirement too literally, since it does not explicitly state to not refetch, just to simply cancel the ongoing request. Makes more sense like this though...

[staltz]

Problem:

Down button should be enabled to click in this situation.

[Retozi]

This is done to avoid entering uncharted territory. It is stated that only one request after another should be fired.

If I enable the upscroll here, it would technically mean that two requests could be pending at the same time. (request triggering going up and going down the list would be independent).

From the feel of it, hyperturtle's solution does exactly this (although I have not verified it in the code). If this is okey, I will enable this.

alternatively I could

1. Avoid the problem by only allowing one scrolldown (like salista)
2. define a priority (up before down, farthest away from scroll pos) of your choice

please advise