Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

core-graph

/core-graph

Pomaga w kodzie dotyczącym relacji Element i Page w Application Builder oraz AutomationNode i AutomationWorkflow w Automation Builder: umieszczanie w kontenerach, przechodzenie drzewa, krawędzie węzłów i nawigacja.

Repozytorium
baserow ↗
Licencja
MIT
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pomaga w kodzie dotyczącym relacji Element i Page w Application Builder oraz AutomationNode i AutomationWorkflow w Automation Builder: umieszczanie w kontenerach, przechodzenie drzewa, krawędzie węzłów i nawigacja.

Oryginalny opis (EN)

Use this skill when working on code involving Element/Page relationships in the Application Builder (contrib/builder) or AutomationNode/AutomationWorkflow relationships in the Automation Builder (contrib/automation). This includes bugs, new features, or refactoring involving node/element placement, element place_in_container, container elements, parent/child/sibling traversal, node edges, or next/previous navigation between points.

Jak działa

  1. What this is
  2. Core abstractions
  3. Design principles
  4. Key files
  5. How Application Builder uses it
  6. How Automation Builder uses it
  7. Common operations
  8. Common pitfalls
  9. Testing
Sekcje z nagłówków SKILL.md, w oryginale · 68 linii, 734 słów
Podgląd SKILL.md
---
name: core-graph
description: Use this skill when working on code involving Element/Page relationships in the Application Builder (contrib/builder) or AutomationNode/AutomationWorkflow relationships in the Automation Builder (contrib/automation). This includes bugs, new features, or refactoring involving node/element placement, element place_in_container, container elements, parent/child/sibling traversal, node edges, or next/previous navigation between points.
---

# Core graph

## What this is

The `core/graph` package contains a reusable graph which the Application and Automation Builder (in `contrib/builder` and `contrib/automation` respectively) rely on.

In the Application Builder, it is used to manage and traverse the relationship between `Element`.

In the Automation Builder, it is used to manage and traverse the relationship between `AutomationNode`.

## Core abstractions

- A graph is made up of **points**. This term is deliberately abstract — what a point represents varies between modules (see "How X Builder uses it" sections below).
- An **edge** connects points. Edge semantics also vary per module (see "How X Builder uses it" sections below).
- Points can be **traversed** to determine the "next", "previous", and "parent" points.
- The graph itself is a **JSON object**.
- The graph is stored on a Django **container model** that implements `GraphModelMixin`. Individual **point models** implement `GraphPointMixin`, which provides helpers for traversal, parent access, edge labels, etc.
- An empty string (`""`) consistently represents the default/fallback edge throughout the system — in edge dictionaries, in `children` maps, and in migration from legacy formats.

## Design principles

- **`core/graph` must remain module-agnostic.** No references to `Element`, `AutomationNode`, or any other module-specific concept should appear in `core/graph` code.
- **Push module-specific logic out.** If a feature in the Application or Automation Builder has requirements specific to that module, the reusable parts belong in `core/graph` and the module-specific code belongs in the consuming module.

## Key files

- `src/baserow/core/graph/` - the directory containing the graph system.
- `tests/baserow/core/graph/` - the directory for all backend graph system tests.
- `src/baserow/core/graph/handler.py` — contains the `BaseGraphHandler`
- `src/baserow/core/graph/models.py` — contains the two Django `Model` mixins.


## How Application Builder uses it

- The container model is `Page`; the point model is `Element`.
- Most points won't have an edge, it'll just be a blank string. If, however, the element's parent implements `ContainerElementTypeMixin`, then its edge is the element's `place_in_container`. For example:
    - `element1` is a `ColumnElement` (so its type is `ColumnElementType`, which implements `ContainerElementTypeMixin`). This column has `column_amount=3`.
    - `element2` is a `HeadingElement`. We want it in the second column. We will make its parent `element1`, and set its `place_in_container` to "1".
- At the moment, there is at most one edge between elements, and it's always a string (whether blank, or a numeric `place_in_container`).

## How Automation Builder uses it

- The container model is `AutomationWorkflow`; the point model is `AutomationNode`.
- Points in automation builder can have one or more edges. They can be found by fetching the service, and calling `get_edges`. For example:
    - `node1` is an `AutomationNode`.
    - `service1 = node1.service.specific.get_type()` gives me `node1`'s service type.
    - `service1.get_edges()` returns a dictionary defining the edges between my nodes.
    - Most node services `get_edges` calls will return `{"": {"label": ""}}`. This represents a straight traversal without an edge name — the outer dictionary key of `""` is the default-edge convention (see Core abstractions). The `label` in the inner dictionary is a user-configured label they can see in the UI.
    - The `CoreRouterServiceType` however will return a UUID for the outer dictionary key, for each edge the user has configured, and a default edge (which is the fallback). E.g.
        - `{"condition1Uuid": {"label": "Condition1"}, "condition2Uuid": {"label": "Condition2"}, "": {"label": "Default fallback"}}`

## Common operations

- Given a container model instance, call `.get_graph()` to get the graph handler. This is the standard entry point for inserting, removing, or moving points. Example: `page.get_graph()` in the Application Builder, `workflow.get_graph()` in the Automation Builder.
- Given a point model instance, the `GraphPointMixin` methods provide traversal helpers (next/previous/parent), edge label access, and related operations. Prefer these over hand-rolling traversal logic.

## Common pitfalls

- In the graph, `children` does not contain *all* child points, only the "first" child of the container. To find *all* children, you must choose that first child point, and then keep traversing next until no points remain.
- It is possible to run into a "legacy" `children` that looks like this: `{"children": [7]}`. The `BaseGraphHandler` will support this, and migrate it to the new format: `{"children": {"": [7]}}` (the `""` key follows the default-edge convention described in Core abstractions).

## Testing

- Ensure any handler modifications are tested in its test file, `test_graph_handler.py`.
- Ensure any model mixin modifications are tested in their test file, `test_graph_models.py`.
- Test fixtures and configuration can be found in the test directory's `fixtures.py` and `conftest.py`.

Wersje

W bazie nie ma innych skilli o nazwie core-graph.

Migawka bazy z 13.11.2026 · wersja paczki 0a805cd84b60 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90Add Or Update Builder Element Type
    Dodaje lub zmienia typ elementu w kreatorze aplikacji Baserow, od modeli backendu po komponenty frontendu i testy.
  • 100test-data-builder
    Prawdopodobnie pomaga budować dane testowe wzorcem Test Data Builder w automatyzacji testów.
  • 100create-update-service
    Tworzy lub aktualizuje typy integracji i usług Baserow, w tym usługi jako źródła danych Application Builder, akcje workflow Buildera, akcje i wyzwalacze węzłów Automation oraz źródła danych dashboardów.
  • 100global-library
    Opisuje model obiektowy GlobalLibrary w TIA Portal: przechodzenie po bibliotece, umieszczanie elementów, klasyfikacja typów, MasterCopy, pliki .zap i .zal oraz zmiana nazw po umieszczeniu.
  • 90Node-RED
    Pomaga tworzyć wizualne automatyzacje Node-RED dla Home Assistant: JSON przepływów, trigger-state, api-call-service, węzły funkcji, kontekst, timery, obsługa błędów i węzły websocket.
  • 100gpui-elements
    Tworzy i składa elementy UI w GPUI: drzewa elementów, własne komponenty, układy i warunkowe renderowanie.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.