Description of problem: Search engine : There is inconsistency for objects entities fields names , especially for fields which consists of multiple words: For example: Mixed : VM : cpu_usage , loggedinuser , datacenter , network_usage Without underscore : Template : creationdate , childcount Only underscore: allow_snapshot , disk_type Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Only underscores are for new objects such as Volumes and Disks
miki - please decide on convention. we can fix all to new convention for auto complete, but will need to make sure we support those changed in syntax for backward compatibility
note that for new fields in 3.1 we don't have to preserve backward compatibility if we change them.
I would go with no underscore.
(In reply to comment #4) > I would go with no underscore. What about Uppercase/Lowercase in other words: allow_snapshot for example : 1) AllowSnapshot 2) allowsnapshot 3) allowSnapshot What should we choose for that ?
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.