Futile | A super simple Unity 2D framework | Game Engine library

You would find life much easier if you used the fable package instead of the forecast package. It handles weekly data better, and it allows forecasts of multiple series at once.

Here is an example using your data. First, we turn the data into a tsibble object, which is the construction needed for fable. It is like a data frame except it has a time index, and an optional key to define separate time series.

geom_area is a special case of geom_ribbon which starts at 0. Use geom_ribbon and specify ymin and y:

You can use dtypes to classify, group by string and date type columns, and aggregate numeric columns respectively.

I was able to figure it out myself actually, for anyone who was interested. It's probably not the cleanest way to do it, but the outcome is producing exactly what I needed.

Rather than running the unstoppable forEach() loop, I just grabbed the entire database, and then later defined it, and pulled ONLY the values.

See the code below that effectively checks to if all values across the DB includes our particular value.

Inside the makGt function, you'll need to get() the value of the object (which is in your case, get the dataframes created by purrr from fName).

Here you go. Pretty straight forward.

I'm going to answer my own question after my investigation.

It is not obvious (at least not to me) in Spring's documentation here that the CustomRepository/Impl mechanism must only be used for a single repository. If you want to create some custom implementation to be inherited by multiple repositories, you'll have to customize the base repository, which is going to be used to back all repository beans.

So I ended up adding an int myTestMethod(OffsetDateTime threshold) implementation to the base repository impl BaseRepositoryImpl. This method will be used to back the method declared in MyEntityDataRepository which extends TestRepository. Note: you must let your repository to extend the interface that declares the custom method. Otherwise, the function in the base repository impl will not be available to the repository bean which is a proxy for the interfaces only, not the base repository impl.

Also, you can actually override the base repository's implementation if you customize the same method in the entity repository.

This is not ideal, but it works. I'd hope I can restrict the custom method availability to some repositories only. One way to do that is to split the different "groups" of repositories into separate disjoint packages and declare a distinct base-class for each separate search path. But that may not make sense in many cases.

The clicking of the button problem is the fact your div overlays the button so when you click, you click on the div, not the button.

For the layout, there is many ways to tackle it. One way is just to use some relative and absolute positioning.

Try using the Unicode values instead of backquoting the literal: