agentleFS
KotlinKotlin/dataframe/dataframe-json/AGENTS.md

dataframe / dataframe-json

AGENTS.md1.1k starsChanged 26 days agoApache-2.0View on GitHub

Guidance for this module. See the root AGENTS.md for repo-wide build/style/KoDEx rules; only module-specific details are here. dataframe-json (artifact dataframe-json, "Kotlin DataFrame JSON integration"). Reads JSON into a DataFrame/ DataRow with schema/type inference, and serializes frames back to JSON. Built on kotlinx.serialization (serialization-core, serialization-json are exposed as api). Depends only on core. This module is a dependency of several others (dataframe-csv, and it's a testImplementation of core) because JSON is how nested DataFrame/DataRow values are encoded inside other formats and…

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 3 mentionsJun 2026: 8 mentionsJul 2026: 7 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 12 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the Kotlin/dataframe repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about Kotlin/dataframe

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Bluesky (51 times).

On GitHub · 50

45 more on GitHub

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All are DataFrame.Companion / DataRow.Companion / AnyFrame / AnyRow extensions:

    line 20
  2. Very specific:

    Run just this module: ./gradlew dataframe-json:test (add -Pkotlin.dataframe.debug=true to match CI checks).

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md — dataframe-json

Guidance for this module. See the root AGENTS.md for repo-wide build/style/KoDEx rules; only module-specific details are here.

What this module is

dataframe-json (artifact dataframe-json, "Kotlin DataFrame JSON integration"). Reads JSON into a DataFrame/ DataRow with schema/type inference, and serializes frames back to JSON. Built on kotlinx.serialization (serialization-core, serialization-json are exposed as api). Depends only on core.

This module is a dependency of several others (dataframe-csv, and it's a testImplementation of core) because JSON is how nested DataFrame/DataRow values are encoded inside other formats and how frames are rendered.

Compiles as a friend of core: build.gradle.kts sets friendPaths to the core project, so this module can use core's internal declarations. Keep that in mind — code here may call internals not visible to normal consumers.

Public API surface (src/main/kotlin/.../io/json.kt)

All are DataFrame.Companion / DataRow.Companion / AnyFrame / AnyRow extensions:

  • Reading: readJson (from File/Path/String path/URL/InputStream) and readJsonStr (from a JSON string), each available for both DataFrame and DataRow.
  • Writing: toJson / writeJson (to File/Path/String/Appendable) for frames and rows.
  • toJsonWithMetadata(...) — emits JSON plus type metadata; used specifically by the Kotlin Notebook IntelliJ plugin for rich rendering. Not a general-purpose serializer.

Key reading behavior to understand before touching inference:

  • TypeClashTactic (in json.kt) controls what happens when the same JSON path holds different shapes across records. ARRAY_AND_VALUE_COLUMNS (default) builds a ColumnGroup with value/array/unwrapped-object columns; ANY_COLUMNS produces a single Any column. The KDoc on the enum has worked examples — read it first.
  • keyValuePaths: List<JsonPath> — at these paths a JSON object is read as a FrameColumn<NameValueProperty> (key/value rows) instead of a ColumnGroup. Use for maps with dynamic/unbounded keys.
  • unifyNumbers — promotes mixed numeric types in a column to a common widest type (UnifyingNumbers).

Extensibility points: CustomEncoder (plug in serialization for otherwise-unsupported value types during write) and Base64ImageEncodingOptions (image → Base64, with gzip / size-limit flags), used by the notebook rendering path.

Implementation lives in impl/io/readJson.kt (readJsonImpl) and impl/io/writeJson.kt (encodeFrame, encodeRow, encodeDataFrameWithMetadata); BytesUtils.kt and compression.kt are internal helpers. JsonFacadeForDebugger.java is a small Java shim used by the debugger integration.

Public API note

binary-compatibility-validator guards the API (see root AGENTS.md for the apiDump/apiCheck flow). Module-specific: the @Deprecated(level = HIDDEN) readJson(stream, ...) overloads exist purely for binary compatibility — leave them in place.

Tests

  • JUnit 5 (useJUnitPlatform()), kotest assertions. Main tests: JsonTests.kt, ImageSerializationTests.kt.
  • Fixtures in src/test/resources/ (repositories.json, imgs/).
  • Run just this module: ./gradlew dataframe-json:test (add -Pkotlin.dataframe.debug=true to match CI checks).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.