[
https://issues.apache.org/jira/browse/TINKERPOP-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896201#comment-16896201
]
ASF GitHub Bot commented on TINKERPOP-2271:
-------------------------------------------
spmallette commented on pull request #1167: TINKERPOP-2271 Add
warnings=true|false console preference (tp34)
URL: https://github.com/apache/tinkerpop/pull/1167
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Priority: Minor
>
> 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)
