Skip to content
Snippets Groups Projects
  1. Mar 16, 2020
  2. Mar 14, 2020
  3. Mar 12, 2020
  4. Mar 02, 2020
  5. Feb 27, 2020
  6. Feb 26, 2020
  7. Feb 24, 2020
  8. Feb 05, 2020
  9. Jan 31, 2020
  10. Jan 29, 2020
  11. Jan 25, 2020
  12. Jan 23, 2020
  13. Jan 16, 2020
  14. Jan 07, 2020
  15. Dec 23, 2019
  16. Dec 16, 2019
  17. Dec 13, 2019
  18. Dec 10, 2019
  19. Dec 06, 2019
  20. Nov 27, 2019
  21. Nov 19, 2019
  22. Nov 14, 2019
  23. Oct 17, 2019
  24. Oct 04, 2019
  25. Oct 03, 2019
  26. Sep 18, 2019
  27. Sep 16, 2019
  28. Sep 13, 2019
  29. Sep 04, 2019
  30. Aug 26, 2019
  31. Jun 03, 2019
  32. May 31, 2019
  33. May 22, 2019
  34. May 20, 2019
  35. May 06, 2019
    • Jan Provaznik's avatar
      GraphQL - Add extra complexity for resolvers · 5ee7884d
      Jan Provaznik authored and Ash McKenzie's avatar Ash McKenzie committed
      If a field is a resolver, its complexity is automatically
      increased. By default we add extra points for sort and search
      arguments (which will be common for various resolvers).
      
      For specific resolvers we add field-specific complexity, e.g.
      for Issues complexity is increased if we filter issues by `labelName`
      (because then SQL query is more complex). We may want to tune these
      values in future depending on real-life results.
      
      Complexity is also dependent on the number of loaded nodes, but only
      if we don't search by specific ID(s). Also added complexity is limited
      (by default only twice more than child complexity) - the reason is
      that although it's more complex to process more items, the complexity
      increase is not linear (there is not so much difference between loading
      10, 20 or 100 records from DB).
      5ee7884d
  36. Apr 29, 2019
  37. Apr 23, 2019
  38. Mar 05, 2019
  39. Feb 21, 2019
Loading