You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2019/07/30 14:56:00 UTC
[jira] [Closed] (TINKERPOP-2271) Add console preference to control
server-originated warning display
[ https://issues.apache.org/jira/browse/TINKERPOP-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-2271.
---------------------------------------
Resolution: Done
Assignee: stephen mallette
Fix Version/s: 3.5.0
3.4.3
> Add console preference to control server-originated warning display
> -------------------------------------------------------------------
>
> Key: TINKERPOP-2271
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2271
> Project: TinkerPop
> Issue Type: Improvement
> Components: console
> Affects Versions: 3.4.2
> Reporter: Dan LaRocque
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.4.3, 3.5.0
>
>
> This follows up on TINKERPOP-2216, which introduced a new status attribute for transmitting warning messages from a remotely executing Gremlin session to the client. Those warning messages are now displayed in the console. They can't be suppressed.
> This issue would add some type of lever to {{gremlin-console}} so that users can disable display of these server-originated warnings, if desired.
> I'm not sure what form that lever should take. Considering that it would be a client-side control, how about a new {{Preferences}} entry, accessible through {{:set warnings true|false}}? That was my best guess at a natural implementation, but maybe there is a better way.
> I'll open a PR with the {{:set warnings true|false}} approach just to facilitate discussion, but of course, feel free to close it and take a different tack.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)