1. 08 Jan, 2020 1 commit
  2. 04 Jan, 2020 1 commit
  3. 02 Dec, 2019 1 commit
  4. 26 Nov, 2019 1 commit
  5. 25 Nov, 2019 1 commit
    • Florian Müllner's avatar
      pasteManager: Catch newly-added gjs exception · 13578c7e
      Florian Müllner authored
      gjs 1.58.2 started throwing an exception when encountering a parameter that
      is an array of plain structs, as that case is not currently supported.
      
      The exception is overly broad though, and also broke the one case that is
      supported: An empty array where the actually struct type isn't relevant.
      
      We cannot fix this in Polari, but at least we can catch the exception to
      fail gracefully, so only DND drop target support gets broken instead of
      the whole interface.
      
      #114
      13578c7e
  6. 11 Nov, 2019 1 commit
  7. 01 Nov, 2019 1 commit
  8. 30 Oct, 2019 1 commit
  9. 08 Oct, 2019 1 commit
  10. 02 Oct, 2019 1 commit
  11. 26 Sep, 2019 1 commit
  12. 18 Sep, 2019 3 commits
  13. 14 Sep, 2019 1 commit
  14. 13 Sep, 2019 1 commit
  15. 12 Sep, 2019 1 commit
    • Florian Müllner's avatar
      Revert "ci: Import run-eslint script from gnome-shell" · 2399228d
      Florian Müllner authored
      Filtering errors by changed lines in a merge request means some
      errors can slip through, for example when an import becomes unused
      but isn't removed.
      
      That's more common than rules changing behind our back, so revert
      to running eslint directly again.
      2399228d
  16. 09 Sep, 2019 2 commits
  17. 06 Sep, 2019 2 commits
  18. 05 Sep, 2019 1 commit
  19. 04 Sep, 2019 3 commits
  20. 02 Sep, 2019 1 commit
  21. 01 Sep, 2019 1 commit
  22. 31 Aug, 2019 1 commit
  23. 30 Aug, 2019 1 commit
  24. 25 Aug, 2019 4 commits
  25. 24 Aug, 2019 1 commit
  26. 21 Aug, 2019 1 commit
  27. 20 Aug, 2019 2 commits
  28. 17 Aug, 2019 1 commit
  29. 14 Aug, 2019 2 commits
    • Florian Müllner's avatar
      cleanup: Always use type-safe comparisons · c6c8202a
      Florian Müllner authored
      The type coercion performed by the regular == and != operators can
      have surprising results. It is therefore considered good practice
      to use the type-safe === and !== variants instead.
      
      !133
      c6c8202a
    • Florian Müllner's avatar
      cleanup: Don't use comparison operator when checking falsy values · 50c3ad1a
      Florian Müllner authored
      We mostly use the regular == and != comparison operators over their
      type-safe === and !== counterparts. This is about to change, but there
      are some places where we don't care whether a value is null, undefined
      or 0; just check for falsiness there instead of using operators, so
      we can start to consistently use the type-safe operators everywhere
      else in a follow-up commit.
      
      !133
      50c3ad1a