throughout | End-to-end testing | Automation library

This will work:

You have the right idea about passing props to your CustomTable component to be able to change the data that gets rendered. Then, the parent component can pass the rows through the CustomTable component's props.

Here's a simplified example

If you use DontDestroyOnLoad it is "forever" you don't have to do it for each scene again.

And then note that after that the Start is not called for every scene load again only the first time!

Rather use SceneManager.sceneLoaded like e.g.

You can specify the format for decimal number like this.

I think you can use the following solution. I needed to change the interval dates as the ones you mentioned on your question were not present in the data set and would lead to an empty data set after filtering. Here we first transform our preferred dates to Date class within interval function from lubridate package. Then we filter our data set for only those rDates that fall within this interval.

You may try this -

The CodePen demo, modified as described, seems to work. Here is what I did:

1. Replace HTML with HTML from your question.
2. Replace {{temp_df | safe}} with simple HTML table.

So it seems there is not enough information to fully answer your question. Something not described in your question is probably causing the unexpected behavior.

Some ideas:

1. The button on your web site apparently behaves differently from the button in the CodePen demo. What does your button do?
2. What HTML does temp_df result in?
3. Are there any JavaScript errors/warnings in the browser dev console?
4. Was any part of the CodePen demo improperly copied? (Copy-paste error.)

Here is my best guess: Examine the code related to localStorage. That is the part of the code we have been shown with the highest chance of running differently between runs.

The original CodePen demo used localStorage as an ad hoc "database" to store information in the browser. However, I presume your website wants to read and write data from a real database that is not localStorage.

Just removing all code related to localStorage may solve your problem.

I you are loading static javascript files I really would not recommend trying to insert variables into that code.

Instead, think about how you would provide that to your javascript code.

You could send it to that code as an argument.

/(?=TITLE: )/g seems like a reasonable start. I'm not sure if the gutter of 2 characters whitespace is in your original text or not, but adding ^ or ^ to the front of the lookahead is nice to better avoid false-positives, i.e. /(?=^TITLE: )/mg, /(?=^ TITLE: )/mg or /(?=^ *TITLE: )/mg.