Ghost | 微影，一款纯粹的在线视频App，基于Material Design MVP RxJava Retrofit | Model View Controller library

This section is currently inaccessible via the API.

This means there's an error in either getServerSideProps or an API route, which is throwing a 500 on the server. You are correct this isn't shown in the console, because it's not happening on the client side.

Inside Vercel, you can view the Functions tab for real-time logs. Then, hit this error again and you'll be able to see the stack trace. If you can't reproduce it, set up logging with a Log Drain so you can track when it does happen.

https://vercel.com/docs/logs

You were pretty much there. Keep up !!

Following is the working code, i was able reproduce on my sandbox. https://codesandbox.io/s/github/devpandya/SamplSignIns/tree/main/?file=/src/SignForms.js

I found 2 issues:

1. The App.css in vanila.js was different then in your React Code. just copy it from your Vanila Code
2. use containerActive state to maniplulate classes in container div.

If your object has properties that are "indexes" (numeric strings in range 0 .. 2^32-1), these properties are always enumerated is sorted numeric order. There's no way you can change that.

Have your server app return data in a more reasonable format, like an array of number-string pairs or an array of objects {id, value}. If this is not possible, convert your object to the said format on the client side, for example:

There seems to be a few problems I would like to point out that should be corrected.

1. It is not JSON.map but some list of objects (maybe assesments.map).
2. I think Panel has to be a direct decendent of Collapse so it should not be in a div tag.
3. Key property should be index so that not all panels have key 1

Here you have a example using map https://codesandbox.io/s/mystifying-microservice-tuef7?file=/index.js

Please ask any questions if this did not answer your question.

You could use sorted(by:) and compare cases that start with "g" and then fallback to normal String comparison if that doesn't happen:

I think you've put your finger on it. When you say animatingDifferences is to be false, you are asking the diffable data source to behave as if it were not a diffable data source. You are saying: "Skip all that diffable stuff and just accept this new data." In other words, you are saying the equivalent of reloadData(). No new cells are created (it's easy to prove that by logging), because all the cells are already visible; but by the same token, all the visible cells are reconfigured, which is exactly what one expects from saying reloadData().

When animatingDifferences is true, on the other hand, the diffable data source thinks hard about what has changed, so that, if necessary, it can animate it. As a result of all that work behind the scenes, therefore, it knows when it can avoid reloading a cell if it doesn't have to (because it can move the cell instead).

Indeed, when animatingDifferences is true, you can apply a snapshot that reverses the cells, and yet configure is never called again, because moving the cells around is all that needs to be done:

MDN says (I'm paraphrasing) that layerX is position of the mouse cursor relative to the clicked element or one of it's parents that is absolutely positioned element

Your ghosty-box is position: absolute, which means that is it's clicked, the layerX is relative to it. If you could position it relatively or using margins, that would solve the issue.

Other option is using pageX or screenX and computing the offset yourself, or positioning an overlay element over the minimap and catching the click on that.

You just have to identify those elements (and I think you can do so using the class with a css selector), then loop through the elements and append the text to the appropriate array.