Much of the past guidance (from 2011, 2012 and 2014 linked above in the question) has suggested that these questions are off topic.
From Question about naming conventions "not constructive"?
Questions on StackExchange sites need to be presented in such a way that there can be an answer that is "the answer". As I read the question, every possible answer to it would be equally valid.
The question asks:
how should I represent the separate words in the filename?
I don't see how this can be answered where there aren't 15 different answers, giving 15 different opinions, all equally valid.
As for other naming convention questions being valid, thanks for bringing them up, we'll go through them and clean up those that slipped through the cracks. The fact that they exist on the site, doesn't make this one or any future questions more constructive.
As noted in Are "name that thing" questions on-topic?
I think there's a difference between questions that ask for a proper term for a concept and questions that ask for naming suggestions for a class or a method.
The former would be fine, in my opinion, but the latter do not belong on Stack Exchange for reasons of being both too localized and entirely discussion-oriented.
There are two types of name questions that are fairly consistently asked, though one can blend into the other. And we continue to get both types of questions - the "what should I name" and "what is the name of". This makes it difficult to provide the answer and easily risk getting too many poor quality answers.
Context: When this question was written, many naming questions were getting closed with a custom off topic message referencing Let's Play the Guessing Game. Prior to that questions were often being closed as "Not Constructive." This is saying that these questions are on topic, though frequently have other problems (getting closed as primary opinion or too broad when there isn't any help given to answers to say what a good answer to the question is nor inspiring answers that meet the ideals of Good Subjective, Bad Subjective. Furthermore, the questions often get down voted for lack of research. It is my hope that by following these points below that the questions can overcome these difficulties and have a chance at remaining open.
These questions are marginally on topic. However, these questions are often poor and without additional information they should be closed as too broad or primarily opinion. Much of the historical guidance points to this being the case.
In an effort to try to make these questions better fit the Q&A format rather than being a poll of answers where "I think it is an XYZ" and "Have you considered XWZ?" we need to help the questions be better asked so that they don't generate one sentence answers and stay away from the questions not to ask so that they have the "long, not short, answers". From the blog post Good Subjective, Bad Subjective:
Great subjective questions tend to have long, not short, answers. The best subjective questions inspire your peers to share their actual experiences, not just post a mindless one-liner or cartoon in hopes of being rewarded with upvotes for being merely “first.” Sharing an experience takes at least one paragraph; ideally several paragraphs. If I’m asking about how to bake cookies, don’t give me a list of grocery items: milk. butter. vanilla. eggs. There is virtually nothing I can learn from a short, static list of grocery items that make up a recipe. Instead, tell me what happened the last time you made cookies from that recipe! Share your detailed experiences, so that we all might learn from them.
To this end, we need to provide some guidance that will help people avoid asking the questions that will be nothing more than a poll of word ideas, pattern names, and guessing at what was intended (and would get closed as either primarily opinion or too broad). Secondly, we should try to help people ask questions that won't be down voted for "this question does not show any research effort" (from the mouseover text on the down vote triangle).
We have exactly the same problem that English.SE does with their own single word requests - lots of them, low quality, uninteresting, attract poor answers from users, and they get complained about in chat, they attract less active users and repel more active users.
Drawing from English.SE tag: single-word-requests and Against single word requests there is a set of questions that are necessary to make these questions better:
- Describe exactly the context that the name or terminology is used
- Describe the criteria for acceptance
- Without some criteria for acceptance of the term, there is no way to say which one is better than another and the question is simply a poll for people to toss out suggestions for a name.
- Which names/terms have you thought of and discarded as inappropriate?
- Just asking for a name doesn't let us know which direction you have thought and as described in Why is research important? we need to know what you have already thought of and discarded.
- Does the question show that you searched for a suitable word before asking the question?
- Without the information to show that you have tried, such questions reek of intellectual laziness. The use of Google is not hard. Sometimes these words are right there if you just enter the language of choice and the code construct you are working with. Stack exchange is not and should never be a "I don't know, I'll ask what its called on P.SE and see if anyone answers"
Given the above pieces of information being provided in the question, it might be acceptable to keep the question open.
I also strongly want people to look at the English.SE tags: https://english.stackexchange.com/tags and note that Single-word-requests on that site make up an average of 30/week or about 1/5th of all of their questions on a day to day basis.
Do we, P.SE, want to have a similar bit of 1/5th of our questions be questions about what to name some 'pattern' or what a particular structure is called within some code?