1. Since it works for entities and terms, the name/namespace would be better not to include "entity".
2. While the project name has the term "views" in it, the namespace itself does not include it + it is accustomed for views-related modules to have a views_* namespace.

...so, based on points 1 and 2 above it should be something like views_reference_filter and the project name "Views Reference Filter".

Perhaps adding the term "nested" would be a good idea too.

Comments

maximpodorov’s picture

Do you suggest to change the project name (system name) while more than 300 sites use the module?

klonos’s picture

Yes, I realize that this is bad practice. What you could do instead is this:

1. Start a new project with a more proper name that matches the views_* ecosystem.
2. Copy the code from here.
3. Deprecate this one by posting a notice in the project's page.
4. Move this project's issues to the queue of the new project (there are only a few and I will even help you with that).

I'm sure that there is another step that would be more tedious/hard/time-consuming and that would be offering a migration path from the old module. I don't know how hard that would be.

Alternatively, you can simply ignore this and wontfix the issue, it's just that the name of the project makes it hard to communicate what it does + some people like myself have certain obsessions like having all views-related modules listed together in their file system.

PS: If you do chose to close this issue, could you please change the casing on the project's name (both in the .info file as well as here in d.o) - it should be with first letters capital: Entityreference Views Filter. See here more info about that: Writing module .info files (Drupal 7.x):

name (Required)
This displays the name of your module, which will appear on the Modules page. Since module names are proper names, it should be capitalized as a proper name (e.g., "Really Neat Widget", not "really neat widget" or "Really neat widget"), and it should be a human-readable name (not really_neat_widget). If your module name includes an acronym (CSS, WYSIWYG, UI, etc.) or a third-party trade name (jQuery, JavaScript), of course follow the standard capitalization for those.

name = Really Neat Widget

maximpodorov’s picture

I'd prefer just to change the long name of the module. Which one is better:
Views Reference Filter
Views Entityreference Filter
Views Reference Filter for Views
or maybe another name?

klonos’s picture

I would go with "Views Reference Filter", but it's up to you.

maximpodorov’s picture

Issue summary: View changes
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.