naming-conventions

问题 I have a model named "clothing" which I want to be the singlular (one piece of clothing). By default, rails says the plural is clothings. Right or wrong, I think it will be more readable if the plural is "clothes". How do I override the plural naming convention? Can I do it right in the model so I don't have to do it over and over? How will this change how routes are handled (I am using restful architecture)? 回答1: I'm no RoR expert, but did find a possible approach. From the referenced site

问题 I'm really trying to understand CakePHP's naming conventions and the following isn't entirely intuitive to me. Let's say I have two pieces of information: videos - specific information about video category - list of categories with id, title, description How would I structure my tables? My first instinct is: videos categories video_categories Is this right? 回答1: It should be: videos categories categories_videos (plural model names in alphabetical order for HABTM) If your videos can only

问题 Just before you say this is a duplicate, I saw the other questions already and I still wanted to post this. So I was reading Thinking in Java -Bruce Eckel and this passage is about the lowercase naming convention: In Java 1.0 and Java 1.1 the domain extensions com , edu , org , net , etc., were capitalized by convention, so the library would appear: NET.mindview.utility.foibles . Partway through the development of Java 2, however, it was discovered that this caused problems, so now the entire

问题 I'm looking for the official naming convention in Java regarding accessors. I've seen that, for instance, the JPanel class deprecated the size() method in favor of getSize() . But in the ArrayList class, the method is size() . So I'm wondering if accessors should be named getXXX() or xXX() ? 回答1: It's usually a bad idea to not use the JavaBeans convention (getters and setters). They're used through reflection by many frameworks, in particular with EL where sometimes you can't access your

问题 I'm setting up a React project with my team that will use mobX as state manager, plus TypeScript. I've seen a common pattern in the casing and naming patterns in React Projects: Non-React Folders and Files: camelCase or kebab-case React (inside components folder): PascalCase Is there a formal convention for folder/file naming in react? If not, is there a style guide on which this pattern is based? Or a reason why this one is used most of the times? 回答1: Just to add my two cents. As others

问题 What is the naming convention used for the Python wheels at Christoph Gohlke's Unofficial Windows Binaries for Python Extension Packages? For example, for scipy here are two of names of wheels on the page: scipy-0.17.0-cp27-none-win32.whl scipy-0.17.0-cp27-none-win_amd64.whl What does 'none' indicate? What's the difference between win32 and win_amd64? Does it matter if I'm using the x86 or x86-64 version of Python (ref Python 2.7.11)? 回答1: Actually that's the wheel tool "naming convention".

问题 Something I see ppl define the variable like this: b2World *_world; b2Body *_body; CCSprite *_ball; instead of b2World *world; b2Body *body; CCSprite *ball; I familiar with the second one, but not the first one. So, I checked the Wikipedia about naming convention: Names beginning with double underscore or an underscore and a capital letter are reserved for implementation (compiler, standard library) and should not be used (e.g. __reserved or _Reserved). So, is that any special meaning which

问题 In the companies I've been working, I've seen a lot the use of prefixes to indicate the scope or the origin of variables, for example m for classes members, i for methods intern variables and a (or p ) for methods parameters: public class User { private String mUserName; public String setUserName(final String aUserName) { final String iUserName = "Mr " + aUserName; mUserName = iUserName; } } What do you think about it? Is it recommended (or precisely not)? I found it quite ugly in a first

问题 Microsoft says fields and properties must differ by more than just case. So, if they truly represent the same idea how should they be different? Here's Microsoft's example of what not to do: using System; namespace NamingLibrary { public class Foo // IdentifiersShouldDifferByMoreThanCase { protected string bar; public string Bar { get { return bar; } } } } They give no guidance on how this should look. What do most developers do? 回答1: No, Microsoft says publicly visible members must differ by

问题 I've been quoting this segment from Sun's document for the past few days, and only now do I stop and think about what it's saying, and I can't make any sense of it. Please keep in mind that English is not my first language. Naming conventions Variables: Except for variables, all instance, class, and class constants are in mixed case with a lowercase first letter . How is this making sense? Isn't this saying that class names are in mixed case with a lower-case first letter? Like I should name