Missing global entity support for Views.

There is no hook_views_data defined. Which poses some questions:

- not sure why this does seem to work for Nodes, just not other entities (like Paragraphs)
- project page reports over 2k sites using this module.. is it possible not one of those is on a non core entity?

Also, i am surprised that the rate.views.inc file is loaded on its own (it does seem to be; just didnt know that was a thing).

So adding this code to rate.module (or i guess rate.views.inc since it seems to get automatically loaded) does provide the Rate widget field for a Paragraph view:

/**
 * Implements hook_views_data().
 */
function rate_views_data() {
  $data['views']['rate_widget_field'] = [
    'title' => t('Rate widget'),
    'help' => t('An instance of a Rate Widget.'),
    'field' => [
      'id' => 'rate_widget_field',
    ],
  ];
  return $data;
}

but it still doesn't work as there are no options to set the column which holds entity id. I'll sort that out next.

i fixed the id not listing the views fields but thee are bigger issues here when trying to render the widget. Basically it looks like the code tries to simplify not requiring relationships.. but then doesnt take into account related data.

For example, my view is listing paragraphs but i am trying to vote on a paragraph which is a child of that main paragraph. I have the correct pid as my field that i use in the widget settings; but in the render code it doesnt use this and ends up using the parent pid. I'll sort this out on Monday.

I changed the title to better describe the issue here. Basically 2 issues:

1. generic entities are not supported (easily fixed with code posted above).

2. related content not supported.

For #2 i went through the render code and it is not correct for handling related content. The module's custom views field does have a setting to select which field is used to get attached entity id for the entity which has the rate widget; but this information is not used in the code. It gets the entity from the base entity of the result row. Of course views doesn't make this easy for us to get row result but it is available. I'll see if i can figure out how to properly access it. The other missing piece would be that i am not sure the view result would know the entity type that the id value is for. It may only know the row base entity (which is what the code currently is using).

My other option would be to try to arrange my setup so that the views base paragraph is the one being voted on rather than its parent; but certainly easier if this module supported related content.

patch for code from #2

rather than try to sort out the issue with using the correct data selected in the field config; i created a separate view using the child paragraph as the base. Then using the https://www.drupal.org/project/views_field_view → module to embed this in my original view. Not ideal from a performance perspective; but works well.