Data Options button on card report

[ftrotter]

The tablular and graph report has this lovely "Data Options" button that is auto-generated from the Socket/Wrench System.

The Card Report view needs the same button. The layout should float the button to the right of the main report title to save vertical space.

The card view is basically just a blade looping through various html layers (its gotten much smarter lately) that displays the data in a particular order with a specific bootstrap based html pattern. It would be best if the "Data Options" button were something that could be modular enough that it would sit at the top of the report.. perhaps that would be something that would work on any fork of the card report for other layout purposes...

[kchapple]

@ftrotter @seanccsmith This is done. I added a CardTest report to LoreCommander to test.

I also added eager-loading of sockets to the wrench model, so all associated sockets will be automatically joined and added to the wrench model when fetched by eloquent. This should fix the performance issue in the defaultSocket check. I left that code commented-out though because I'm not sure what dataset to test on.

The CardTest report also has an example of creating on-demand sockets and wrenches in the report constructor, which might be interesting. In the constructor, we create the sockets and wrenches, or get them from the database if they already exist. That looks like this:

`
public function __construct(?string $Code, array $Parameters = [], array $Input = [])
{
$wrench = Wrench::firstOrCreate([
'wrench_lookup_string' => 'CardTest_music_filter',
'wrench_label' => 'Card Type Filter'
]);

    $socket1 = Socket::firstOrCreate([
        'wrench_id' => $wrench->id,
        'socket_value' => "`type` = 'music'",
        'socket_label' => "Music Cards",
        'is_default_socket' => 1,
        'socketsource_id' => 0
    ]);

    $socket2 = Socket::firstOrCreate([
        'wrench_id' => $wrench->id,
        'socket_value' => "`type` = 'video'",
        'socket_label' => "Video Cards",
        'is_default_socket' => 0,
        'socketsource_id' => 0
    ]);

    parent::__construct($Code, $Parameters, $Input);
}

`
Here's what it should look like:

[ftrotter]

Hey Ken, I finally found some time to test this, and the basic socket wrench lookup seems to fail.
Can you please take a look at the OneR project and help me understand why this is not working?

I am getting the following error message:

I can confirm that I appear to have a properly configured wrench and socket, etc etc...

I am commiting a backup of the databases so that you can build an instance if you would like to debug that way...

[ftrotter]

Also the "data options" button should not appear unless there is at least one working wrench.. otherwise it is just something to click on and get back "there are no data options configured for this report". No Data Options... should mean no Data Options button...

-FT