27 Matching Annotations
  1. Aug 2021
    1. Will my code break on Ruby 2.7? A short answer is “maybe not”. The changes in Ruby 2.7 are designed as a migration path towards 3.0. While in principle, Ruby 2.7 only warns against behaviors that will change in Ruby 3, it includes some incompatible changes we consider to be minor. See the “Other minor changes” section for details. Except for the warnings and minor changes, Ruby 2.7 attempts to keep the compatibility with Ruby 2.6. So, your code will probably work on Ruby 2.7, though it may emit warnings. And by running it on Ruby 2.7, you can check if your code is ready for Ruby 3.0.
  2. Jul 2021
  3. Apr 2021
    1. Lumberjack::Logger does not extend from the Logger class in the standard library, but it does implement a compantible API.
  4. Mar 2021
  5. Feb 2021
    1. I'm not very familiar with this feature. Do you know what version of Rails is required for this code to work? Is it Rails 6.0+? We run the test suite via Travis CI for many versions of Rails so I am concerned that this will cause test failures on older versions. Can we write the tests so that they gracefully exclude the CSP stuff on older versions where CSP is not supported?
    1. Keep in mind that third party code with references to other files also processed by the asset Pipeline (images, stylesheets, etc.), will need to be rewritten to use helpers like asset_path.
    1. {a: 1, b: 2, c: 3, d: 4} => {a:, b:, **rest} # a == 1, b == 2, rest == {:c=>3, :d=>4}

      equivalent in javascript:

      {a, b, ...rest} = {a: 1, b: 2, c: 3, d: 4}
      

      Not a bad replacement for that! I still find javascript's syntax a little more easily readable and natural, but given that we can't use the same syntax (probably because it would be incompatible with existing syntax rules that we can't break for compatibility reasons, unfortunately), this is a pretty good compromise/solution that they've come up with.

  6. Oct 2020
    1. React Final Form was written by the same guy (@erikras) that wrote Redux Form, so much of the API is exactly the same.
    1. The backwards compatible implementation of jsx(...), we would still support key passed as props. We'd just pull it off props and issue a warning that this pattern is deprecated. The upgrade path is to just pass it to JSX separately if you need it.
    1. It's easy to persist the entire application state in a way that is backwards-compatible, so persisted states can survive application changes.
  7. Jul 2020
    1. It does, however, provide the --porcelain option, which causes the output of git status --porcelain to be formatted in an easy-to-parse format for scripts, and will remain stable across Git versions and regardless of user configuration.
  8. May 2020
  9. Apr 2020
  10. Jan 2019
    1. Coming back to the two ‘FreeSync’ settings in the monitor OSD, they differ in the variable refresh rate range that they support. ‘Standard Engine’ supports 90 – 144Hz (90 – 119Hz via HDMI) whilst ‘Ultimate Engine’ gives a broader variable refresh rate range of 70 – 144Hz (62 – 119Hz via HDMI). We didn’t notice any adverse effects when using ‘Ultimate Engine’, so we’d suggest users simply stick to that option.

      In my tests using Standard Engine, in combo with G-Sync Compatible Driver, I get more screen flickering during menus.