An error occurred fetching the project authors.
  1. 16 Sep, 2019 1 commit
  2. 09 Apr, 2019 1 commit
  3. 05 Apr, 2019 2 commits
  4. 01 Feb, 2019 1 commit
  5. 13 Oct, 2018 1 commit
  6. 02 Oct, 2018 1 commit
  7. 01 Oct, 2018 1 commit
    • Oswaldo Ferreira's avatar
      Make single diff patch limit configurable · 4fbca2a3
      Oswaldo Ferreira authored
      - Creates a new column to hold the single patch limit value on
      application_settings
      - Allows updating this value through the application_settings API
      - Calculates single diff patch collapsing limit based on
      diff_max_patch_bytes column
      - Updates diff limit documentation
      - Adds documentation (with warning) as of how one can update this limit
      4fbca2a3
  8. 19 Sep, 2018 1 commit
  9. 18 Sep, 2018 1 commit
  10. 14 Sep, 2018 2 commits
  11. 05 Sep, 2018 1 commit
  12. 04 Sep, 2018 2 commits
  13. 15 Aug, 2018 1 commit
  14. 07 Aug, 2018 1 commit
    • Phil Hughes's avatar
      Web IDE & CodeSandbox · 7b4b9e1c
      Phil Hughes authored
      This enables JavaScripts projects to have live previews straight in the
      browser without requiring any local configuration. This uses the
      CodeSandbox package `sandpack` to compile it all inside of an iframe.
      
      This feature is off by default and can be toggled on in the admin
      settings. Only projects with a `package.json` and a `main` key are
      supported.
      
      Updates happen in real-time with hot-reloading. We just watch for
      changes to files and then send them to `sandpack` to allow it to reload
      the iframe. The iframe includes a very simple navigation bar, the text
      bar is `readonly` to stop users navigating away from the preview and
      the back and forward buttons just pop/splice the navigation stack
      which is tracked by a listener on `sandpack`
      
      There is a button inside the iframe which allows the user to open the
      projects inside of CodeSandbox. This button is only visible on
      **public** projects. On private or internal projects this button
      get hidden to protect private code being leaked into an external
      public URL.
      
      Closes #47268
      7b4b9e1c
  15. 03 Aug, 2018 1 commit
  16. 10 Jul, 2018 1 commit
  17. 26 Jun, 2018 1 commit
  18. 22 Jun, 2018 1 commit
  19. 13 Jun, 2018 1 commit
  20. 08 Jun, 2018 2 commits
    • Bob Van Landuyt's avatar
      Users can accept terms during registration · 3d713ac1
      Bob Van Landuyt authored
      When a user checks the `accept` checkbox, we will track that
      acceptance as usual. That way they don't need to accept again after
      they complete the registration.
      
      When an unauthenticated user visits the `/-/users/terms` page, there
      is no button to accept, decline or continue. The 'current-user menu'
      is also hidden from the top bar.
      3d713ac1
    • Andreas Kämmerle's avatar
      Update settings section titles · 6a077c54
      Andreas Kämmerle authored
      6a077c54
  21. 07 May, 2018 2 commits
  22. 04 May, 2018 2 commits
    • Bob Van Landuyt's avatar
      Enforces terms in the web application · 7684217d
      Bob Van Landuyt authored
      This enforces the terms in the web application. These cases are
      specced:
      
      - Logging in: When terms are enforced, and a user logs in that has not
        accepted the terms, they are presented with the screen. They get
        directed to their customized root path afterwards.
      - Signing up: After signing up, the first screen the user is presented
        with the screen to accept the terms. After they accept they are
        directed to the dashboard.
      - While a session is active:
        - For a GET: The user will be directed to the terms page first,
          after they accept the terms, they will be directed to the page
          they were going to
        - For any other request: They are directed to the terms, after they
          accept the terms, they are directed back to the page they came
          from to retry the request. Any information entered would be
          persisted in localstorage and available on the page.
      7684217d
    • Bob Van Landuyt's avatar
      Store application wide terms · 3d6d0a09
      Bob Van Landuyt authored
      This allows admins to define terms in the application settings.
      
      Every time the terms are adjusted, a new version is stored and becomes
      the 'active' version. This allows tracking which specific version was
      accepted by a user.
      3d6d0a09
  23. 04 Apr, 2018 4 commits
  24. 02 Apr, 2018 1 commit
  25. 29 Mar, 2018 1 commit
  26. 27 Mar, 2018 1 commit
  27. 26 Mar, 2018 3 commits
  28. 12 Jul, 2017 1 commit
  29. 06 Jul, 2017 1 commit