Rails optional validation ambiguous












0














I discovered that this validation still works



validates :name, presence: true, if: (spa) -> { spa.name_required && other_name.blank? }


This has a lambda with an argument, but the argument isn't used for the other_name check



I found that when I removed the argument to the lambda it still works



validates :name, presence: true, if: -> { name_required && other_name.blank? }


The documentation says we should be creating procs, see https://guides.rubyonrails.org/active_record_validations.html#using-a-symbol-with-if-and-unless



I think this works because a lambda is a closure inside the object it's defined so the object's methods are available.



Question is, why does the Active Record documentation say use a proc with an argument? Is using a lambda like this wrong in some way?










share|improve this question






















  • A lambda is bound to its context so the implicit self is the same as the outer context where it was defined. In this case self is the model instance. I think this is just a case of the documentation being old or poorly written as it does not really matter if you use a proc or lambda as long as you understand the differences.
    – max
    Nov 19 '18 at 17:36












  • I think so too, max, but using a lambda is much less clumsy looking :)
    – Ghoti
    Nov 20 '18 at 14:52
















0














I discovered that this validation still works



validates :name, presence: true, if: (spa) -> { spa.name_required && other_name.blank? }


This has a lambda with an argument, but the argument isn't used for the other_name check



I found that when I removed the argument to the lambda it still works



validates :name, presence: true, if: -> { name_required && other_name.blank? }


The documentation says we should be creating procs, see https://guides.rubyonrails.org/active_record_validations.html#using-a-symbol-with-if-and-unless



I think this works because a lambda is a closure inside the object it's defined so the object's methods are available.



Question is, why does the Active Record documentation say use a proc with an argument? Is using a lambda like this wrong in some way?










share|improve this question






















  • A lambda is bound to its context so the implicit self is the same as the outer context where it was defined. In this case self is the model instance. I think this is just a case of the documentation being old or poorly written as it does not really matter if you use a proc or lambda as long as you understand the differences.
    – max
    Nov 19 '18 at 17:36












  • I think so too, max, but using a lambda is much less clumsy looking :)
    – Ghoti
    Nov 20 '18 at 14:52














0












0








0







I discovered that this validation still works



validates :name, presence: true, if: (spa) -> { spa.name_required && other_name.blank? }


This has a lambda with an argument, but the argument isn't used for the other_name check



I found that when I removed the argument to the lambda it still works



validates :name, presence: true, if: -> { name_required && other_name.blank? }


The documentation says we should be creating procs, see https://guides.rubyonrails.org/active_record_validations.html#using-a-symbol-with-if-and-unless



I think this works because a lambda is a closure inside the object it's defined so the object's methods are available.



Question is, why does the Active Record documentation say use a proc with an argument? Is using a lambda like this wrong in some way?










share|improve this question













I discovered that this validation still works



validates :name, presence: true, if: (spa) -> { spa.name_required && other_name.blank? }


This has a lambda with an argument, but the argument isn't used for the other_name check



I found that when I removed the argument to the lambda it still works



validates :name, presence: true, if: -> { name_required && other_name.blank? }


The documentation says we should be creating procs, see https://guides.rubyonrails.org/active_record_validations.html#using-a-symbol-with-if-and-unless



I think this works because a lambda is a closure inside the object it's defined so the object's methods are available.



Question is, why does the Active Record documentation say use a proc with an argument? Is using a lambda like this wrong in some way?







ruby-on-rails validation activerecord






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 14:41









Ghoti

2,20611519




2,20611519












  • A lambda is bound to its context so the implicit self is the same as the outer context where it was defined. In this case self is the model instance. I think this is just a case of the documentation being old or poorly written as it does not really matter if you use a proc or lambda as long as you understand the differences.
    – max
    Nov 19 '18 at 17:36












  • I think so too, max, but using a lambda is much less clumsy looking :)
    – Ghoti
    Nov 20 '18 at 14:52


















  • A lambda is bound to its context so the implicit self is the same as the outer context where it was defined. In this case self is the model instance. I think this is just a case of the documentation being old or poorly written as it does not really matter if you use a proc or lambda as long as you understand the differences.
    – max
    Nov 19 '18 at 17:36












  • I think so too, max, but using a lambda is much less clumsy looking :)
    – Ghoti
    Nov 20 '18 at 14:52
















A lambda is bound to its context so the implicit self is the same as the outer context where it was defined. In this case self is the model instance. I think this is just a case of the documentation being old or poorly written as it does not really matter if you use a proc or lambda as long as you understand the differences.
– max
Nov 19 '18 at 17:36






A lambda is bound to its context so the implicit self is the same as the outer context where it was defined. In this case self is the model instance. I think this is just a case of the documentation being old or poorly written as it does not really matter if you use a proc or lambda as long as you understand the differences.
– max
Nov 19 '18 at 17:36














I think so too, max, but using a lambda is much less clumsy looking :)
– Ghoti
Nov 20 '18 at 14:52




I think so too, max, but using a lambda is much less clumsy looking :)
– Ghoti
Nov 20 '18 at 14:52












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376978%2frails-optional-validation-ambiguous%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376978%2frails-optional-validation-ambiguous%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

SQL update select statement

'app-layout' is not a known element: how to share Component with different Modules