Clean up configuration

Closing this outdated, since on 2.0.x it was only possible to use this module for node entity types. With 3.0.x branch it possible to use for other entity types, eg. taxonomy terms, so having prevnext_enabled_entity_types is required.

Thanks @sokru! I'm using 3.x, and my config has

prevnext_enabled_entity_types:
  node: node
prevnext_enabled_entity_bundles:
  node:
    page: page

There's no need for prevnext_enabled_entity_types because node is already present within prevnext_enabled_entity_bundles if you see what I mean.

Thanks!

@AndyF perhaps you could prepare a MR to remove it and make it clear by code?

Thanks @anybody. I'd be happy to write the code, but there's enough open issues that are more important, I'd rather wait for them to get merged (to avoid both stealing time from them, and possible conflicts).

Just to make the suggestion crystal clear (hopefully), the following would indicate that prev/next is enabled for the page and article bundle of the node entity type and the tags bundle of the taxonomy_term entity type.

prevnext_enabled_entity_bundles:
  node:
    page: page
    article: article
  taxonomy_term:
    tags: tags

Thanks