ecoportal-api-graphql 2.0.0 → 2.2.1

data/lib/ecoportal/api/graphql/base/CLAUDE.md

@@ -1,50 +0,0 @@
-# base
-
-Data-only model base classes — these declare fields and structure but hold no `client`, no query resolvers, and no business logic.
-
-## Contents
-
-| File / class | Purpose |
-|---|---|
-| `action.rb` / `Base::Action` | Action fields (id, name, status, dates, assignee IDs); declared `root!` so excluded from cascaded diffs |
-| `action_category.rb` / `Base::ActionCategory` | Action category fields |
-| `contractor_entity.rb` / `Base::ContractorEntity` | Contractor entity fields |
-| `contractor_entity/member_changes.rb` | Nested member-changes sub-model |
-| `date_time.rb` / `Base::DateTime` | Wraps `{ dateTime:, timeZone: }` response objects |
-| `delta_result.rb` / `Base::DeltaResult` | `pageDelta` result item: `id` + `delta` enum (UPDATED/NOT_FOUND/NEW) |
-| `field.rb` / `Base::Field` | Generic field model |
-| `file_attachment.rb` / `Base::FileAttachment` | File attachment metadata |
-| `file_container.rb` / `Base::FileContainer` | File container wrapper |
-| `location_classification_type.rb` | Classification type (name) |
-| `location_node.rb` / `Base::LocationNode` | Location node with ancestors and classifications |
-| `location_structure.rb` / `Base::LocationStructure` | Location structure tree model |
-| `location_structure/draft.rb` | Draft structure model |
-| `location_structure/draft/structure.rb` | Nested draft structure detail |
-| `organization.rb` / `Base::Organization` | Thin organization base (id, name) |
-| `page.rb` | Namespace module; requires `basic`, `data_field`, `section`, `section_collection`, `phased` |
-| `page/basic.rb` / `Base::Page::Basic` | BasicPage — inherits `Interface::BasePage`; no extra fields |
-| `page/phased.rb` / `Base::Page::Phased` | PhasedPage — inherits `Interface::BasePage`; `embeds_many :stages` |
-| `page/phased/stage.rb` / `Base::Page::Phased::Stage` | Single stage: id, name, ordering, state, sections, components |
-| `page/section.rb` / `Base::Page::Section` | Section wrapper (ContentSection or SplitSection); merges left/right dataFields into `components` |
-| `page/section_collection.rb` / `Base::Page::SectionCollection` | Enumerable wrapper over sections; provides `get_by_type`, `get_by_heading`, `components` |
-| `page/data_field.rb` / `Base::Page::DataField` | Base data field class; `TYPE_MAP` dispatches `from_doc` to typed subclasses |
-| `page/data_field/` | 10 typed subclasses (PlainText, RichText, DateField, Number, Gauge, People, Select, Checklist, TagField, Geo) + `Collection` |
-| `page_info.rb` / `Base::PageInfo` | Cursor pagination info (endCursor, hasNextPage) |
-| `person_member.rb` / `Base::PersonMember` | Person member (name, email, id) |
-| `preview_page.rb` / `Base::PreviewPage` | Lightweight page preview (no field data) |
-| `resource.rb` / `Base::Resource` | Resource model (inherits `Logic::BaseModel` directly) |
-| `pages_workflow.rb` / `Base::PagesWorkflow` | PagesWorkflow top-level model: `autoPageCreationEnabled`, `fields` (RegisterField), `stages`; sub-files under `pages_workflow/` cover RegisterField, CallbackType, OperationInterface, TriggerInterface, and supporting types |
-
-## Conventions
-
-- `Base::` classes are data-only: `passkey`, `passthrough`, `passboolean`, `passarray`, `embeds_one`, `embeds_many` only — no business methods, no resolvers.
-- `Model::` subclasses in `../model/` add `class_resolver` wiring and may add behaviour (e.g. `Model::Page::Phased#stages` wraps the array in `Compat::StageCollection`).
-- `Interface::BasePage` is the shared parent of both `Basic` and `Phased`; field declarations that apply to both page types live there.
-- `Base::Action` declares `root!` — this marks it as an independent server entity, excluded from cascaded `as_update` diffs.
-- When adding a new field to a page type, add it to `Interface::BasePage` if it applies to both, or to the appropriate `Base::Page::*` class.
-
-## Related
-
-- `../interface/base_page.rb` — common parent for Basic + Phased page base classes
-- `../model/` — concrete models that subclass these bases
-- `../model/page_union.rb` — factory that dispatches `__typename` to `Model::Page::Basic` or `Model::Page::Phased`

data/lib/ecoportal/api/graphql/builder/CLAUDE.md

@@ -1,65 +0,0 @@
-# builder
-
-Façade classes that group related mutations (and occasional queries) under a single object.
-Consumers interact with builders rather than instantiating `Logic::Mutation` / `Logic::Query`
-subclasses directly.
-
-## Contents
-
-| File / class | Exposed from `GraphQL` as | Purpose |
-|---|---|---|
-| `action.rb` / `Builder::Action` | `GraphQL#action` | `create`, `update`, `archive` — wraps `Mutation::Action::*` |
-| `contractor_entity.rb` / `Builder::ContractorEntity` | `GraphQL#contractorEntity` | `create`, `update`, `destroy` — wraps `Mutation::ContractorEntity::*` |
-| `location_structure.rb` / `Builder::LocationStructure` | `GraphQL#locationStructure` | `nodeClassifications` (query), `applyCommandsInput`, `applyCommands`, `draft` sub-builder |
-| `location_structure/draft.rb` / `Builder::LocationStructure::Draft` | via `locationStructure.draft` | Location structure draft mutations |
-| `page.rb` / `Builder::Page` | `GraphQL#page` | Full page lifecycle: `update`, `archive`, `unarchive`, `build_from_template`, `create_from_template`, `create_draft`, `delete_draft`, `publish_draft`, `approve/reject/restart/undo/batch_update_review_task`, `execute_workflow_commands` (new), `execute_force_commands` (deprecated) |
-| `register.rb` / `Builder::Register` | *(not yet exposed)* | **Stub** — all methods commented out. No `Mutation::Register::*` classes exist yet. See TODO below. |
-
-## How builders are exposed
-
-All active builders are wired in `lib/ecoportal/api/graphql.rb` as instance methods:
-
-```ruby
-def page
-  Builder::Page.new(client)
-end
-def action
-  Builder::Action.new(client)
-end
-# etc.
-```
-
-`registers` (note: plural, lowercase) returns `Compat::Registers`, **not** `Builder::Register`.
-`Builder::Register` is a stub and is not yet wired into the top-level class.
-
-## Builder::Register — TODO
-
-`builder/register.rb` contains a stub class with all methods commented out.
-Before it can be implemented:
-
-1. Research which Register mutations exist in the schema (`createRegister`,
-   `updateRegister`, `archiveRegister`, etc.) — none are currently documented
-   in `.ai-assistance/code/ecoportal_schema_reference.md`.
-2. Create `Mutation::Register::*` + `Input::Register::*` + `Payload::Register::*`
-   following the pattern of `Mutation::Page::*`.
-3. Expose `Builder::Register` from `GraphQL#register` (distinct from `#registers`
-   which is the compat search layer).
-
-Until then, register mutation callers must instantiate `Mutation::Register::*` directly
-(none exist yet), or use `Compat::Registers` for search.
-
-## Conventions
-
-- One builder per domain entity. Sub-builders (e.g. `LocationStructure::Draft`) are
-  nested under their parent builder's folder and exposed via a method on the parent.
-- Builder methods are snake_case public API; private helper methods are camelCase
-  (matching the existing convention: `updateMutation`, `archiveMutation`, etc.).
-- Builders never hold state — each method instantiates a fresh mutation/query object.
-- Builders do not implement pagination; callers use `QueryConnection#each` for that.
-
-## Related
-
-- `../mutation/` — concrete mutation classes that builders delegate to
-- `../query/` — concrete query classes (some builders also expose query shortcuts)
-- `../compat/` — v2-compatible layer (`Compat::Pages`, `Compat::Registers`) that
-  wraps builders + queries with an eco-helpers-compatible interface