12 Matching Annotations
  1. Apr 2022
  2. Jul 2021
  3. Mar 2021
  4. Feb 2021
    1. Using a terminus to indicate a certain outcome - in turn - allows for much stronger interfaces across nested activities and less guessing! For example, in the new endpoint gem, the not_found terminus is then wired to a special “404 track” that handles the case of “model not found”. The beautiful thing here is: there is no guessing by inspecting ctx[:model] or the like - the not_found end has only one meaning!
    2. A major improvement here is the ability to maintain more than two explicit termini. In 2.0, you had the success and the failure termini (or “ends” as we used to call them). Now, additional ends such as not_found can be leveraged to communicate a non-binary outcome of your activity or operation.
  5. May 2020
    1. This topic is not a support question

      This is hard to answer because I don't know what they classify as a "support question". For example, are bugs classified as a support question? So if it's a bug, should I check this or no?

      What is the purpose of this checkbox? If you could describe that, it would make it much easier to answer the question.

  6. Apr 2020
    1. Just as with wine-tasting, having a bigger vocabulary for colours allows specific colours to be perceived more readily and remembered more easily, even if not done consciously.
  7. Mar 2020
    1. in which case the consent must be given on the basis of sufficiently precise information, including information on the lack of protection in the third country