Skip to content

mxcli syntax lookup misses common statement verbs (grant) and two-level names (integration message-definition) #1389

Closed
ako/mxcli
#1127

Description

@MohamedGamalEzzatAli

Environment: mxcli v0.25.0.

What happens

  • mxcli syntax grant → Unknown topic: grant, although grant is a listed keyword of the security entity-access page (Keywords: entity access, grant, revoke, …).
  • mxcli syntax integration message-definition → No topic "integration.message-definition". Showing 1 topic(s) matching "message-definition". This one recovers, but only through the fallback.

Why it matters

People and coding agents look a statement up by its verb first (grant, revoke, alter, refresh). An "Unknown topic" sends them to guess the syntax, which is exactly what mxcli syntax exists to prevent.

Feature suggestions

  1. Resolve a single word against the topics' keywords (not only their paths) and show the best matches, as the multi-word fallback already does.
  2. Verb aliases: grant / revoke → security entity-access (plus the microflow/page access topics), so the common verbs never hit "Unknown topic".
  3. mxcli syntax --search <words> that prints ranked topic paths, for tooling that wants the path rather than the page.

Activity

  1. github-actions commented on Oct 11, 2026

    @github-actions

    Issue Triage

    Summary:
    The mxcli syntax command fails to recognize single‑word verbs like grant and two‑level names such as integration message-definition, returning “Unknown topic” or relying on a fallback instead of directing users to the correct syntax page.

    Checklist of required information (bug report)

    Required info Present? Notes
    mxcli version ✅ mxcli v0.25.0 given
    Mendix version of the project ❌ Not mentioned
    Scenario (what the user was trying to do) ✅ Running mxcli syntax grant and mxcli syntax integration message-definition
    Expected output ✅ Should resolve to the appropriate syntax topic (e.g., security entity-access)
    Experienced output ✅ “Unknown topic: grant” and fallback behavior for integration message-definition
    AI bug report (session log or mxcli diag --bundle) ❌ Not provided

    Missing information:

    • The Mendix version (e.g., 9.x, 10.x) of the project you’re working with.
    • A diagnostic bundle or session log from mxcli diag --bundle (or at least the relevant log excerpt) to help reproduce the issue.

    Could you please add those details? Once we have them, we’ll be able to investigate and address the problem more effectively. Thanks for reporting this!


    Automated triage via OpenRouter — workflow source

  2. MohamedGamalEzzatAli commented on Oct 11, 2026

    @MohamedGamalEzzatAli
    Author

    Thanks for the triage. No diag bundle here: the session logs on this machine also cover an unrelated proprietary project, and the two commands in the description reproduce it directly.

    Environment: mxcli v0.25.0 (2026-10-05 build), Windows 10.

    Mendix version: not project-dependent (mxcli syntax reads no project); observed with Studio Pro 11.12.1 installed.

  3. added a commit that references this issue on Oct 12, 2026
  4. added 2 commits that reference this issue on Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions