ALIFE

Today I want to try something different to handle a ReactNode variable that could be change with my

so I take it as an object, and it`s key is number, value is the ReactNode i want.

everything was ok;

but when I click the button and trigger the onCance error occured! like this

but why? I had bind this in the constructor; i dont know. Here is part of my code

That statement pasted in my question was copied from https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements#Using_the_lifecycle_callbacks.

As a no-experience developer with Webcomponent, I am trying to understand all rule-of-thumbs and best practices recommended so far.

Continuing reading it says "... use Node.isConnected to make sure". It is quite obvious what it means: check if it is still connected but it is not clear, at least for me, what I should do to workaround it or what I should expect in some circustances.

My case is I am creating a Webcomponent to listen SSE (Server Sent Events). This will be usefull for a alife dashboard and several other scenarios. The SSE event will be basically responded either by NodeJs or Spring Webflux after consumed from Kafka Stream.

All simple examples I did so far I didn't face any issue with element not longer connected during connectedcallback.

Additionally, I didn't read any recommendation in Best Practices regard "element no longer connected".

I read few excellent discussions:

can-a-custom-elements-connectedcallback-be-called-more-than-once-before-disc

from where I learned that I can always trust in this lifecycle constructor --> connectedCallback --> disconnectedCallback.

And

How to have a 'connectedCallback' for when all child custom elements have been connected

where basically I learned there is not a specific method "called after all children were upgraded"

Both questions pass close to my question but it doesn't answer me: which challenge or risk should be aware of or how to workaround the possibility to "connectedCallback may be called once your element is no longer connected"? In my scenario described above is there any treatment I am missing? Should I created some observer that triggers when the element is not longer available to recreate an eventsource object and add again a Listener to such eventsource object?

I pasted the code bellow for ilustration and the complete Webcomponent example can be cloned from https://github.com/jimisdrpc/simplest-webcomponet and its backend from https://github.com/jimisdrpc/simplest-kafkaconsumer.

I have two split windows in Vim (left one is my_file.txt, right one is terminal) with the help of rightb vert term in ".vimrc". For closing both windows I usually use exit in terminal and then :q for my_file.txt. But if I close windows in other order (first comes :q for file and then exit for terminal) process "Vim" is still alife and a window with my_file is opened. So I need to use :q one more time for closing my_file window. Can you suppose the reason?

I observe a node by simply doing

Say I have a service that I want to resolve with a scoped lifetime. But sometime I try to resolve it as the interface type and sometimes at the implementation type.

The first thing I tried to do was this:

I have a project which pulls in two local packages. My stack.yaml has:

I have created a script that scrape website: 1688.com and the problem is, the site is in Chinese so whenever i try to retrieve the text, it gives me a bunch of unicode and when i export to a CSV file, there's nothing in the file. My code: