Skip to content
Snippets Groups Projects
  1. Dec 03, 2019
  2. Oct 04, 2019
  3. Jun 25, 2019
  4. Jun 21, 2019
  5. Jun 03, 2019
  6. Apr 25, 2019
  7. Apr 17, 2019
    • Sean McGivern's avatar
      Only use backslash escapes in autocomplete when needed · 67b16f7e
      Sean McGivern authored
      Autocompletion for references happens on the frontend. Those references
      are turned into actual references on the backend, but only after
      Markdown processing has happened. That means that if a reference
      contains a character that Markdown might consume, it won't render
      correctly. So we need to do some escaping on the frontend.
      
      We have these potential problem characters:
      https://docs.gitlab.com/ee/user/markdown.html#emphasis
      
      1. ~ - this is ~~strikethrough~~, but only when doubled.
      2. _ - used for _emphasis_, doubled is __bold__.
      3. * - also used for *emphasis*, doubled is **bold** also.
      4. ` - used for `code spans`, any number works.
      
      We don't need to escape `-` any more. When it comes to being inside a
      word:
      
      1. a~~b~~ has strikethrough, so it needs to be escaped everywhere.
      2. a_b_ has no emphasis (see [a]) so it only needs to be escaped at the
         start and end of words.
      3. a*b* has emphasis, so it needs to be escaped everywhere.
      4. a`b` has a code span, so it needs to be escaped everywhere.
      
      Or, in code terms:
      
      1. Always escape ~~, *, and ` when being inserted by autocomplete.
      2. Escape _ when it's either at the beginning or the end of a word.
      
      [a]: https://docs.gitlab.com/ee/user/markdown.html#multiple-underscores-in-words
      67b16f7e
  8. Apr 10, 2019
  9. Mar 07, 2019
    • Tim Zallmann's avatar
      Moved all emojis to the public folder · d07919de
      Tim Zallmann authored
      Created new emojis map in public folder
      
      Renamed folder to emojis
      
      Loading now the emojis from Localstorage or from Server
      
      Moved all emojis to the public folder
      
      Loading the emojis.json file now through AJAX
      
      Loads now the map in the web element instead when building the emoji tag
      
      Updated the custom Element Setup to modern method
      
      Fixed Emoji Karma Specs for async loading
      
      Loading now the emojis from Localstorage or from Server
      
      Loads now the map in the web element instead when building the emoji tag
      
      Fixed problem with FIXTURE_PATH for emojis fixtures
      
      Fixes Linting Error in gemojione.rake
      
      Fixed Emoji Karma Specs
      
      Fix static type check in gemojione and check if already registered
      
      Testing if the Emoji Support Check is failing Rspec
      
      Change of CLass Name, returning true on check to test
      
      Fixes failing Emoji RSpec Tests
      
      Moved Emojis into public/-/emojis/1/
      
      Fixed Linting Errors in gl_emoji
      
      Fix to fixtures creation for emojis
      
      Fixed path spec for new subdirectory -/emojis
      
      Optimized emojis.json output
      
      Fix for Emoji Spec failure due to unicode dataset
      
      Better catch handling for emojis
      d07919de
  10. Feb 25, 2019
    • Martin Wortschack's avatar
      Style avatars for groups and projects · 12ed4dbf
      Martin Wortschack authored and Filipa Lacerda's avatar Filipa Lacerda committed
      - Add rectangular avatar classes
      - Update avatar for groups
      - Update avatar for projects
      - Update avatar for frequent items
      - Update avatar on "Fork project" page
      - Conditionally add rectangular avatar class to autocomplete items
      12ed4dbf
  11. Jan 07, 2019
  12. Dec 20, 2018
  13. Nov 21, 2018
  14. Nov 12, 2018
  15. Oct 31, 2018
  16. Oct 19, 2018
  17. Oct 05, 2018
  18. Jul 02, 2018
  19. Jun 25, 2018
  20. May 04, 2018
  21. Mar 29, 2018
    • Sean McGivern's avatar
      Escape autocomplete results for Markdown · 78aa8c16
      Sean McGivern authored
      A label name can contain a `_`, `~~`, or other Markdown-significant
      characters. But label references are processed _after_ Markdown processing has
      run, so we can't easily fix this on the backend.
      
      We can make it more convenient, though, by changing the frontend to escape these
      characters so they aren't processed as Markdown, when we insert them from
      autocomplete.
      78aa8c16
  22. Mar 11, 2018
  23. Mar 09, 2018
  24. Jan 29, 2018
  25. Jan 08, 2018
  26. Nov 28, 2017
  27. Nov 13, 2017
  28. Aug 03, 2017
  29. Jul 07, 2017
  30. Jun 29, 2017
  31. Jun 28, 2017
  32. Jun 27, 2017
  33. Jun 23, 2017
  34. Jun 15, 2017
  35. Jun 05, 2017
  36. May 16, 2017
  37. May 03, 2017
Loading