Skip to content
Snippets Groups Projects
Select Git revision
  • move-gl-dropdown
  • improve-table-pagination-spec
  • move-markdown-preview
  • winh-fix-merge-request-spec
  • master default
  • index-namespaces-lower-name
  • winh-single-karma-test
  • 10-3-stable
  • 36782-replace-team-user-role-with-add_role-user-in-specs
  • winh-modal-internal-state
  • tz-ide-file-icons
  • 38869-milestone-select
  • update-autodevops-template
  • jivl-activate-repo-cookie-preferences
  • qa-add-deploy-key
  • docs-move-article-ldap
  • 40780-choose-file
  • 22643-manual-job-page
  • refactor-cluster-show-page-conservative
  • dm-sidekiq-versioning
  • v10.4.0.pre
  • v10.3.0
  • v10.3.0-rc5
  • v10.3.0-rc4
  • v10.3.0-rc3
  • v10.3.0-rc2
  • v10.2.5
  • v10.3.0-rc1
  • v10.0.7
  • v10.1.5
  • v10.2.4
  • v10.2.3
  • v10.2.2
  • v10.2.1
  • v10.3.0.pre
  • v10.2.0
  • v10.2.0-rc4
  • v10.2.0-rc3
  • v10.1.4
  • v10.2.0-rc2
40 results

application_controller.rb

Forked from GitLab.org / GitLab FOSS
Source project has a limited visibility.
  • Sean McGivern's avatar
    3f71c43e
    Allow setting content for resolutions · 3f71c43e
    Sean McGivern authored
    When reading conflicts:
    
    1. Add a `type` field. `text` works as before, and has `sections`;
       `text-editor` is a file with ambiguous conflict markers that can only
       be resolved in an editor.
    2. Add a `content_path` field pointing to a JSON representation of the
       file's content for a single file.
    3. Hitting `content_path` returns a similar datastructure to the `file`,
       but without the `content_path` and `sections` fields, and with a
       `content` field containing the full contents of the file (with
       conflict markers).
    
    When writing conflicts:
    
    1. Instead of `sections` being at the top level, they are now in a
       `files` array. This matches the read format better.
    2. The `files` array contains file hashes, each of which must contain:
       a. `new_path`
       b. `old_path`
       c. EITHER `sections` (which works as before) or `content` (with the
          full content of the resolved file).
    3f71c43e
    History
    Allow setting content for resolutions
    Sean McGivern authored
    When reading conflicts:
    
    1. Add a `type` field. `text` works as before, and has `sections`;
       `text-editor` is a file with ambiguous conflict markers that can only
       be resolved in an editor.
    2. Add a `content_path` field pointing to a JSON representation of the
       file's content for a single file.
    3. Hitting `content_path` returns a similar datastructure to the `file`,
       but without the `content_path` and `sections` fields, and with a
       `content` field containing the full contents of the file (with
       conflict markers).
    
    When writing conflicts:
    
    1. Instead of `sections` being at the top level, they are now in a
       `files` array. This matches the read format better.
    2. The `files` array contains file hashes, each of which must contain:
       a. `new_path`
       b. `old_path`
       c. EITHER `sections` (which works as before) or `content` (with the
          full content of the resolved file).