Skip to content

Playground: Make "Ambiguous Alternatives" visible for the user #267

@Lotes

Description

@Lotes

Here's an example of a user writing a grammar in the Playground and not seeing the "Ambiguous Alternatives Detected" parser error, which is only printed in the console:
eclipse-langium/langium#1259

We should make such parser validation errors visible in the Playground UI.

Originally posted by @spoenemann in #130 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingplaygroundIssues related to the playground functionalits

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions