Skip to content

Add adapter compatibility docs for LookML, Cube, OSI, and Malloy#109

Merged
nicosuave merged 1 commit intomainfrom
nicosuave/lookml-compat-docs
Mar 28, 2026
Merged

Add adapter compatibility docs for LookML, Cube, OSI, and Malloy#109
nicosuave merged 1 commit intomainfrom
nicosuave/lookml-compat-docs

Conversation

@nicosuave
Copy link
Copy Markdown
Member

Summary

  • Adds docs/compatibility/ with feature-by-feature compatibility documentation for the LookML, Cube, OSI, and Malloy adapters.
  • Each doc covers every concept in the source format and marks it as supported, partial support (with explanation), or unsupported.
  • Properties that parse without error but have no Sidemantic equivalent are grouped as "not mapped" per section.

Comprehensive feature-by-feature documentation of what each adapter
supports, partially supports, or does not support when importing from
these semantic layer formats.
@nicosuave nicosuave merged commit 0ee407d into main Mar 28, 2026
14 checks passed
@nicosuave nicosuave deleted the nicosuave/lookml-compat-docs branch March 28, 2026 14:16
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 63801aefb8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

| `source: name is base -> { ... } extend { ... }` (pipeline source) | Partial support: the extend block is processed but the arrow pipeline query is not evaluated. The model has no table and only contains fields from the extend block. |
| `source: name is compose(...)` (composite sources) | Partial support: parses without error but the composition logic is not evaluated. No fields are extracted from the composed sources. |
| `source()` (parameterized sources) | Partial support: parameters are parsed by the grammar but parameter values are not stored or substituted. |
| Old `+` syntax for extending (`base + { ... }`) | Partial support: the grammar parses this as `SQRefinedQuery`. The extend block is not processed, only the base source reference. |
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Mark old + source extension as unsupported

The compatibility table says source: name is base + { ... } keeps the base source reference, but the adapter never handles SQRefinedQuery in MalloyModelVisitor._process_sq_expr (it only branches on SQTable, SQSQL, SQExtendedSource, SQInclude, SQID, and SQParens). For Malloy files using the legacy + form, this means neither the base source nor refinement block is actually applied, so users can end up with models missing table/sql and extracted fields despite docs claiming partial support.

Useful? React with 👍 / 👎.

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.

1 participant