tabla | Modern Periodic Table | Build Tool library

Here is one way you could do: I changed geom_bar with geom_col anc put an ifelse in geom_text(). Here you can define the position 0,-1,1.5` of the numbers.

Remove "dataSrc": "" - you should not need to use the dataSrc option at all, because it looks as if your JSON row data is already in a top-level named array: { ... "data": [...] ... }.

By default, the name used by DataTables for the row iteration entry point is data. So, not using dataSrc at all is the same as using "dataSrc": "data".

If you use "dataSrc": "", that is telling DataTables that your row array is in a JSON structure like this - an array of arrays:

As you have a field called ID you can store that in the HTML when you first build your table (in the loop), this can be either as an attribute to the tr, eg

Consider doing this with possibly/safely

Provide a location to write the data in write_json -

They have a common structure by the looks of it. Just extract the t param ,for each link in the link column, and put that into a json url template string:

You can write a series of user defined functions/helpers which extract the expand url in each case and finally grab the details that you want as a dataframe. You can combine all those dataframes into one with map2_dfr from purrr. I use map2_dfr because you also need to alter the index in the nth-child part of the css selector, when retrieving the details you wanted from each li listing. This means the get_details function needs 2 args as input i.e. the url and the index.

map2_dfr() is a variant of map() that allows you to iterate over multiple arguments simultaneously.

One option is to create the child row as a Datatable. Then create a second format function for the child Datatable. You can start with this blog to see how to create a child Datatable. You can ignore the Editor configuration. Also take a look at this example from this thread.

The parent Datatable doesn't know about the content of the child row and the Datatables API's like row().child().show() (here)aren't available. If you don't want the child to be a Datatable then you will need to create the code to show the sub-child rows.

The SQL Script DataSource Initialization feature has been redesigned in Spring Boot 2.5.

By default, data.sql scripts are now run before Hibernate is initialized. This aligns the behavior of basic script-based initialization with that of Flyway and Liquibase. If you want to use data.sql to populate a schema created by Hibernate, set spring.jpa.defer-datasource-initialization to true. While mixing database initialization technologies is not recommended, this will also allow you to use a schema.sql script to build upon a Hibernate-created schema before it’s populated via data.sql.

Reference

Spring Boot 2.5 Release Notes