probo

rohit/probo

Fork 0

Commit Graph

Author	SHA1	Message	Date
Sacha Al Himdani	c635492f75	SOA as document: replace export with publish workflow Statements of Applicability are no longer exported as one-off PDFs. Instead, each SOA owns a persistent document that accumulates versions over time, following the same publish/approve lifecycle as authored documents. Publishing without approvers publishes immediately; publishing with approvers creates a draft pending approval via the existing quorum system. SOAs can also store default approvers that are pre-populated in the publish dialog. The SOA is removed from the snapshot system — applicability statements are now queried directly (snapshot_id IS NULL) rather than through snapshot copies. A standalone migration script (cmd/migrate-soa-snapshots-to-documents) converts existing SOA snapshots into documents with proper ProseMirror content, preserving version history and approval decisions. Signed-off-by: Sacha Al Himdani <sacha@getprobo.com>	2026-04-16 00:01:13 +02:00
Émile Ré	31cca05ca4	Split GraphQL schemas into per-entity files Split each API's monolithic schema.graphql into per-coredata-model files under graphql/ subdirectories. gqlgen's follow-schema layout with {name}.resolvers.go template generates one resolver file per schema file. Relay uses schema + schemaExtensions to load the split files. Connect API: 8 files (base, session, organization, profile, personal_api_key, saml, scim, audit_log) Trust API: 5 files (base, trust_center, auth, nda, mailing_list) Console API: 25 files covering all domain entities Types extended across files (Organization, Mutation, Viewer, TrustCenter, Identity) are defined in base.graphql as required by Relay's schemaExtensions. Signed-off-by: Émile Ré <emile@getprobo.com>	2026-04-15 09:19:38 +04:00

Author

SHA1

Message

Date

Sacha Al Himdani

c635492f75

SOA as document: replace export with publish workflow

Statements of Applicability are no longer exported as one-off PDFs.
Instead, each SOA owns a persistent document that accumulates versions
over time, following the same publish/approve lifecycle as authored
documents.

Publishing without approvers publishes immediately; publishing with
approvers creates a draft pending approval via the existing quorum
system. SOAs can also store default approvers that are pre-populated in
the publish dialog.

The SOA is removed from the snapshot system — applicability statements
are now queried directly (snapshot_id IS NULL) rather than through
snapshot copies.

A standalone migration script (cmd/migrate-soa-snapshots-to-documents)
converts existing SOA snapshots into documents with proper ProseMirror
content, preserving version history and approval decisions.

Signed-off-by: Sacha Al Himdani <sacha@getprobo.com>

2026-04-16 00:01:13 +02:00

Émile Ré

31cca05ca4

Split GraphQL schemas into per-entity files

Split each API's monolithic schema.graphql into per-coredata-model
files under graphql/ subdirectories. gqlgen's follow-schema layout
with {name}.resolvers.go template generates one resolver file per
schema file. Relay uses schema + schemaExtensions to load the split
files.

Connect API: 8 files (base, session, organization, profile,
personal_api_key, saml, scim, audit_log)

Trust API: 5 files (base, trust_center, auth, nda, mailing_list)

Console API: 25 files covering all domain entities

Types extended across files (Organization, Mutation, Viewer,
TrustCenter, Identity) are defined in base.graphql as required by
Relay's schemaExtensions.

Signed-off-by: Émile Ré <emile@getprobo.com>

2026-04-15 09:19:38 +04:00

2 Commits