Of the three solutions only Option 1 is polymorphic. Fields by themselves cannot be overridden. Which is exactly why Option 2 returns the new keyword warning. The solution to the warning is not to append the “new” keyword, but to implement Option 1. If you need your field to be polymorphic you need to wrap … Read more
A one-liner using ES6 arrow function and ternary operator: Object.keys(obj).forEach(key => obj[key] === undefined ? delete obj[key] : {}); Or use short-circuit evaluation instead of ternary: (@Matt Langlois, thanks for the info!) Object.keys(obj).forEach(key => obj[key] === undefined && delete obj[key]) Same example using if statement: Object.keys(obj).forEach(key => { if (obj[key] === undefined) { delete obj[key]; … Read more
You can do it like this: Field[] declaredFields = Test.class.getDeclaredFields(); List<Field> staticFields = new ArrayList<Field>(); for (Field field : declaredFields) { if (java.lang.reflect.Modifier.isStatic(field.getModifiers())) { staticFields.add(field); } }
Jeremy Hicks, thanks for your extension. I didn`t know how to connect your function to doctrine, but finally i find answer. $doctrineConfig = $this->em->getConfiguration(); $doctrineConfig->addCustomStringFunction(‘FIELD’, ‘DoctrineExtensions\Query\Mysql\Field’); I need FIELD function to order my Entities that i select by IN expression. But you can use this function only in SELECT, WHERE, BETWEEN clause, not in ORDER … Read more
Here’s a complete working example: public class Person { public string Name { get; set; } } class Program { static void PropertySet(object p, string propName, object value) { Type t = p.GetType(); PropertyInfo info = t.GetProperty(propName); if (info == null) return; if (!info.CanWrite) return; info.SetValue(p, value, null); } static void PropertySetLooping(object p, string propName, … Read more
A slightly simplified answer: public class Book { private final String title; public Book(String title) { this.title = title; } public Book() { this(“Default Title”); } … }
You can clear the input field by using $(‘#shares’).val(”);
It doesn’t grant you anything extra beyond being concise. If you prefer the more verbose syntax, then by all means, use that. One advantage to using auto props is that it can potentially save you from making a silly coding mistake such as accidentally assigning the wrong private variable to a property. Trust me, I’ve … Read more
Because it breaks encapsulation — this is why most people use accessors heavily. However, if you think it’s the right solution for your task, ignore it (meaning the strict encapsulation complaints) and do what’s right for your project. Don’t let the OO nazis tell you otherwise.
Setting a form element to disabled will stop it going to the server, e.g.: <input disabled=”disabled” type=”text” name=”test”/> In javascript it would mean something like this: var inputs = document.getElementsByTagName(‘input’); for(var i = 0;i < inputs.length; i++) { if(inputs[i].style.display == ‘none’) { inputs[i].disabled = true; } } document.forms[0].submit(); In jQuery: $(‘form > input:hidden’).attr(“disabled”,true); $(‘form’).submit();