Nothing Special   »   [go: up one dir, main page]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Filter warnings are intrusive #1375

Open
jeswr opened this issue Jun 7, 2024 · 2 comments
Open

Filter warnings are intrusive #1375

jeswr opened this issue Jun 7, 2024 · 2 comments
Labels
difficulty:low effort:medium enhancement ☀️

Comments

@jeswr
Copy link
Member
jeswr commented Jun 7, 2024

Issue type:

  • 🐛 Bug

Description:

Filter warnings become intrusive to seeing the result of queries, in particular when running npx -p @comunica/query-sparql comunica-sparql http://www.w3.org/ns/odrl/2/ "CONSTRUCT { ?s ?p ?o } WHERE { ?s ?p ?o filter(contains(?o, \"Purpose\")) }" the result is this which makes it hard to see the single result of

<http://www.w3.org/ns/odrl/2/purpose> <http://www.w3.org/2000/01/rdf-schema#label> "Purpose"@en.

It may be worth considering having a default behavior where there is 1 message at the end saying "Warnings were produced when running this query, use the -w flag to show details".
@github-project-automation github-project-automation bot moved this to Triage in Maintenance Jun 7, 2024
@github-actions GitHub Actions
Copy link
github-actions bot commented Jun 7, 2024

Thanks for reporting!

@rubensworks
Copy link
Member

It may be worth considering having a default behavior where there is 1 message at the end saying "Warnings were produced when running this query, use the -w flag to show details".

Something like that would be useful indeed.
Or perhaps even just showing the first X messages, and then muting similar messages (with another warning to say things were muted). This way we keep streamability.

@rubensworks rubensworks removed this from Maintenance Jun 7, 2024
@github-project-automation github-project-automation bot moved this to Triage in Development Jun 7, 2024
@rubensworks rubensworks moved this from Triage to To do (prio:low) in Development Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
difficulty:low effort:medium enhancement ☀️
Projects
Development
Status: To do (prio:low)
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rubensworks @jeswr