An error occurred fetching the project authors.
  1. 11 Oct, 2018 1 commit
    • Yorick Peterse's avatar
      Support pushing of feature flags to the frontend · 21940d1e
      Yorick Peterse authored
      This adds a method to Gitlab::GonHelper called
      `push_frontend_feature_flag`. This method can be used to easily expose
      the state of a feature flag to Javascript code. For example, using this
      method we may write the following controller code:
      
          before_action do
            push_frontend_feature_flag(:vim_bindings)
          end
      
          def index
            # ...
          end
      
          def edit
            # ...
          end
      
      In Javascript we can then check the state of the flag as follows:
      
          if ( gon.features.vimBindings ) {
            // ...
          }
      
      Fixes https://gitlab.com/gitlab-org/release/framework/issues/17
      21940d1e
  2. 31 May, 2018 1 commit
  3. 29 May, 2018 1 commit
  4. 24 May, 2018 1 commit
  5. 02 May, 2018 1 commit
  6. 05 Mar, 2018 1 commit
  7. 01 Mar, 2018 1 commit
  8. 02 Feb, 2018 1 commit
  9. 03 Jan, 2018 1 commit
  10. 21 Dec, 2017 2 commits
  11. 09 Nov, 2017 1 commit
  12. 22 Sep, 2017 1 commit
  13. 07 Sep, 2017 1 commit
  14. 05 Sep, 2017 2 commits
  15. 31 Aug, 2017 1 commit
    • Sean McGivern's avatar
      `current_application_settings` belongs on `Gitlab::CurrentSettings` · 5883ce95
      Sean McGivern authored
      The initializers including this were doing so at the top level, so every object
      loaded after them had a `current_application_settings` method. However, if
      someone had rack-attack enabled (which was loaded before these initializers), it
      would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
      have that method.
      
      To fix this:
      
      1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
         `Object.new.current_application_settings` to work.
      2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
         like that in several places.
      3. Change the initializers to use that new form.
      5883ce95
  16. 29 Jun, 2017 1 commit
  17. 26 May, 2017 2 commits
  18. 21 May, 2017 1 commit
  19. 18 May, 2017 1 commit
  20. 05 May, 2017 1 commit
  21. 28 Apr, 2017 4 commits
  22. 13 Apr, 2017 1 commit
  23. 14 Mar, 2017 1 commit
  24. 07 Mar, 2017 1 commit
  25. 06 Mar, 2017 2 commits
    • Eric Eastwood's avatar
    • Eric Eastwood's avatar
      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
      e6fc0207
  26. 01 Mar, 2017 1 commit
  27. 23 Feb, 2017 1 commit
  28. 23 Jan, 2017 1 commit
    • Luke Bennett's avatar
      Added raven and raven-vue plugin, updated gon_helper with data needed for... · c252c034
      Luke Bennett authored
      Added raven and raven-vue plugin, updated gon_helper with data needed for raven and created raven_config, required by application.js
      
      Added is_production to define sentry environment
      
      Removed as much jQuery as possible
      
      Added public_sentry_dsn application_settings helper method
      
      Use URI module instead of regex for public dsn
      
      Removed raven-vue and load raven on if sentry is enabled
      
      Add load_script spec
      
      added raven_config spec
      
      added class_spec_helper and tests
      
      added sentry_helper spec
      
      added feature spec
      c252c034
  29. 09 Jan, 2017 1 commit
  30. 14 Dec, 2016 1 commit
  31. 19 Sep, 2016 1 commit
  32. 19 Jul, 2016 1 commit
  33. 28 Jun, 2016 1 commit
    • Paco Guzman's avatar
      Unused got variable with very bad performance · b5fa56eb
      Paco Guzman authored
      In any case if just want the value which is always ‘gitlab’
      
      require 'benchmark/ips'
      
      Project.first # To load database things
      GitlabIssueTrackerService.first # To load database things
      
      Benchmark.ips do |x|
        x.config(:time => 5, :warmup => 2)
      
        x.report("current") do
          Project.new.default_issue_tracker.to_param
        end
      
        x.report("") do
          'gitlab'
        end
      
        x.compare!
      end
      
      Calculating -------------------------------------
                   current     4.000  i/100ms
                              30.938k i/100ms
      -------------------------------------------------
                   current     47.298  (±10.6%) i/s -    232.000 
                                4.366M (±20.9%) i/s -     17.202M
      
      Comparison:
                          :  4366456.0 i/s
                   current:       47.3 i/s - 92318.26x slower
      b5fa56eb