1. 30 Aug, 2019 3 commits
    • Build: Optional skipping of typescript checking in dev bundler (#18772) · 89abc77b
      * Build: Removed typescript checking from dev bundler
      
      - when switching branches and trying out features, TS checking and bundling are eating up a lot
      of CPU
      - most of us are using an editor with typechecking support
      - this commit removes type checking from the dev bundler
      - we still have type checking enabled as a precommit hook and as part of
      the prod bundler
      
      * Adds new npm script: start:noTsCheck
      David committed
    • Docs: Improve API tutorial intro content and readability (#18762) · a928da7f
      * API Tutorial: Improve content and readability
      
      - Simplified the introductory paragraphs.
      - Rewrote the descriptions and steps to improve readability.
      
      * Updated topic as discussed in the PR
      
      - Corrected the typo from "Graphana" to "Grafana".
      - Rewritten the note as suggested by reviewers and to avoid passive voice.
      
      Please review and share your thoughts.
      Kumaraguru Ramasamy committed
    • Panels: Destroy panel model when recreating repeated panels (#18799) · e4a0b224
      Fixes #18533
      
      To recreate the bug described in the original issue in the simplest possible way:
      
      1. Setup dashboard with a single panel and repeat it using variables
      2. Set the dashboard refresh to 5s
      3. Hover over repeated panel during the refresh
      
      What happened there?
      When panels are repeated every time the dashboard is refreshed or variables change the repeated PanelModels are recreated. In https://github.com/grafana/grafana/blob/master/public/app/features/dashboard/state/DashboardModel.ts#L322 the models are removed from dashboard panel's model property what makes the dashboard re-render with source panel only, and then back again with the repeated panels when models are re-created. This means creating new DashboardPanel components. But when the repeated PanelModels are removed, they are not destroyed what results in a behaviour described in #18533.
      
      This is a quick fix for this issue. Ideally I think we should use some cache and update the repeated PanelModels when the refresh or variables change trigger re-render, instead of re-creating those every time. I don't want to do this ATM as the logic around repeating panels is quite complex and require some <3.
      Dominik Prokop committed
  2. 29 Aug, 2019 7 commits
  3. 28 Aug, 2019 7 commits
  4. 27 Aug, 2019 3 commits
  5. 26 Aug, 2019 8 commits
  6. 25 Aug, 2019 2 commits
  7. 23 Aug, 2019 5 commits
  8. 22 Aug, 2019 5 commits