BigW Consortium Gitlab

  1. 28 Apr, 2017 1 commit
  2. 14 Apr, 2017 1 commit
  3. 04 Apr, 2017 2 commits
  4. 17 Mar, 2017 1 commit
  5. 06 Mar, 2017 2 commits
    • Use native unicode emojis · e6fc0207
      Eric Eastwood authored
       - gl_emoji for falling back to image/css-sprite when the browser
         doesn't support an emoji
       - Markdown rendering (Banzai filter)
       - Autocomplete
       - Award emoji menu
          - Perceived perf
          - Immediate response because we now build client-side
       - Update `digests.json` generation in gemojione rake task to be more
         useful and  include `unicodeVersion`
      
      MR: !9437
      
      See issues
      
       - #26371
       - #27250
       - #22474
  6. 01 Mar, 2017 1 commit
  7. 23 Feb, 2017 1 commit
  8. 16 Feb, 2017 1 commit
  9. 10 Feb, 2017 1 commit
  10. 05 Feb, 2017 1 commit
  11. 05 Jan, 2017 1 commit
  12. 06 Dec, 2016 1 commit
  13. 01 Dec, 2016 1 commit
  14. 30 Nov, 2016 3 commits
  15. 28 Nov, 2016 1 commit
    • Speed up Project security access specs · 13ad9a74
      Robert Speicher authored
      Prior, every single test was creating four `ProjectMember` objects, each
      of which created one `User` record, even though each test only used
      _one_ of those Users, if any.
      
      Now each test only creates the single user record it needs, if it needs
      one. This shaves minutes off of each spec file changed here.
  16. 16 Nov, 2016 1 commit
  17. 17 Oct, 2016 1 commit
  18. 30 Sep, 2016 1 commit
  19. 20 Jul, 2016 1 commit
  20. 03 Jun, 2016 2 commits
  21. 18 May, 2016 1 commit
  22. 21 Apr, 2016 2 commits
  23. 06 Apr, 2016 1 commit
  24. 20 Mar, 2016 1 commit
  25. 13 Mar, 2016 1 commit
    • External Users · 42fcd388
      Zeger-Jan van de Weg authored
      The user has the rights of a public user execpt it can never create a project,
       group, or team. Also it cant view internal projects.
  26. 10 Mar, 2016 1 commit
  27. 14 Jan, 2016 2 commits
  28. 24 Dec, 2015 1 commit
  29. 01 Dec, 2015 1 commit
  30. 05 Oct, 2015 2 commits
  31. 02 Oct, 2015 1 commit
    • Basic setup for an RSpec based benchmark suite · 19893a1c
      Yorick Peterse authored
      This benchmark suite uses benchmark-ips
      (https://github.com/evanphx/benchmark-ips) behind the scenes. Specs can
      be turned into benchmark specs by setting "benchmark" to "true" in the
      top-level describe block like so:
      
          describe SomeClass, benchmark: true do
      
          end
      
      Writing benchmarks can be done using custom RSpec matchers, for example:
      
          describe MaruTheCat, benchmark: true do
            describe '#jump_in_box' do
              it 'should run 1000 iterations per second' do
                maru = described_class.new
      
                expect { maru.jump_in_box }.to iterate_per_second(1000)
              end
            end
          end
      
      By default the "iterate_per_second" expectation requires a standard
      deviation under 30% (this is just an arbitrary default for now). You can
      change this by chaining "with_maximum_stddev" on the expectation:
      
          expect { maru.jump_in_box }.to iterate_per_second(1000)
            .with_maximum_stddev(10)
      
      This will change the expectation to require a maximum deviation of 10%.
      
      Alternatively you can use the it block style to write specs:
      
          describe MaruTheCat, benchmark: true do
            describe '#jump_in_box' do
              subject { -> { described_class.new } }
      
              it { is_expected.to iterate_per_second(1000) }
            end
          end
      
      Because "iterate_per_second" operates on a block, opposed to a static
      value, the "subject" method must return a Proc. This looks a bit goofy
      but I have been unable to find a nice way around this.
  32. 06 Sep, 2015 1 commit