CustomConnectorFork

What a fork changes on top of its base. Manifest changes are a JSON merge patch (RFC 7396): an array is replaced whole, so its path is the unit of change and of conflict, and the base's key order holds.

type CustomConnectorFork {
  added_files: [String!]!
  base: CustomConnectorForkBase!
  manifest_paths: [String!]!
  removed_files: [String!]!
  replaced_files: [String!]!
  upstream: CustomConnectorForkUpstream
  upstream_conflicts: [CustomConnectorUpstreamConflict!]!
}

Fields

CustomConnectorFork.added_files ● [String!]! non-null scalar

CustomConnectorFork.base ● CustomConnectorForkBase! non-null object

CustomConnectorFork.manifest_paths ● [String!]! non-null scalar

The manifest values the fork sets or removes, as manifest/<JSON pointer>.

CustomConnectorFork.removed_files ● [String!]! non-null scalar

CustomConnectorFork.replaced_files ● [String!]! non-null scalar

CustomConnectorFork.upstream ● CustomConnectorForkUpstream object

A published fork's standing against its base. Null on a draft.

CustomConnectorFork.upstream_conflicts ● [CustomConnectorUpstreamConflict!]! non-null object

Where upstream changed something the fork also changed; the fork keeps its own version. On a draft each is also an issue (FORK_UPSTREAM_CONFLICT) and publish refuses until all are resolved. On a published version, the conflicts of its build on the base's current content.

Member Of

CustomConnectorVersion object