Skip to content

docs: add collections usage#875

Open
lmeyerov wants to merge 21 commits intofeat/collections-supportfrom
docs/collections-support
Open

docs: add collections usage#875
lmeyerov wants to merge 21 commits intofeat/collections-supportfrom
docs/collections-support

Conversation

@lmeyerov
Copy link
Copy Markdown
Contributor

@lmeyerov lmeyerov commented Dec 29, 2025

Summary

  • clarify collections purpose in the notebook intro and add a layered-highlights callout in 10min
  • rebalance layout settings with lighter collections guidance and an encodings pointer
  • move collections wire-protocol details into the spec and keep examples focused

RTD Preview

Testing

  • not run (docs only)

@lmeyerov lmeyerov force-pushed the docs/collections-support branch 4 times, most recently from 8bee706 to dff95a0 Compare January 5, 2026 07:08
@lmeyerov lmeyerov force-pushed the docs/collections-support branch 4 times, most recently from 531a661 to 017e7f8 Compare January 13, 2026 09:57
@lmeyerov lmeyerov force-pushed the feat/collections-support branch from 3cf9e9d to 41a33c4 Compare January 16, 2026 17:48
@lmeyerov lmeyerov force-pushed the docs/collections-support branch from 099d19c to ad9cb69 Compare January 16, 2026 17:49
@lmeyerov lmeyerov force-pushed the docs/collections-support branch from ad9cb69 to fb58c44 Compare January 16, 2026 20:20
"import graphistry\n",
"from graphistry import collection_set, collection_intersection, n, e_forward, Chain\n",
"\n",
"edges = pd.read_csv(Path('demos/data/honeypot.csv'))\n",
Copy link
Copy Markdown
Contributor

@mj3cheun mj3cheun Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this file is not included in the repo, probably should be or a way to download the data should be provided?

Comment on lines 43 to 54
## Message Structure

All GFQL wire protocol messages are JSON objects with a `type` field that identifies the message type. The protocol uses discriminated unions for polymorphic types.

### Type Identification

Each object includes a `type` field:
- Operations: `"Node"`, `"Edge"`, `"Chain"`, `"Let"`, `"ChainRef"`, `"RemoteGraph"`, `"Call"`
- Predicates: `"GT"`, `"LT"`, `"IsIn"`, etc.
- Temporal values: `"datetime"`, `"date"`, `"time"`

This enables unambiguous deserialization and validation.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not related to added changes:

im a little confused about what messages are? the message types above Chain, Let, Call seem to suggest these are top level but then why are deeper level Node and Edge or even predicates also messages?

also why is there a Protocol Overview section and then a Message Structure section just below it?

Comment on lines +20 to +23
.. note::
Collections are visualization URL settings; apply them after GFQL results
(for example, ``g2.collections(...)``). The GFQL remote/upload APIs do not
accept collections payloads yet.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure why this note was needed but i dont see an issue in having it either

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants