Steve Roughley

What about having a PrettyPrintConfig (for example!) interface and a default implementation which would allow users to create their own configurations without changing the JsonWriter visibility? I would think it...

I guess this is because optionals were new in Java 1.8?

Can yu solve this by creating your own writer? PrettyPrint might show some pointers as to how: https://github.com/ralfstx/minimal-json/blob/master/com.eclipsesource.json/src/main/java/com/eclipsesource/json/PrettyPrint.java

It would be great to have these in the API, but retain the original methods too, which has advantages of not breaking existing API and also avoiding object creation when...

Yes, that was how I understood the suggestion - I would assume in each case the actual method would be something very simple like Optional get(String name) { return Optional.ofNullable(get(name));...

Interesting point. Most of those methods have a default value as a parameter, so would you just put that into e.g. an `OptionalInt` instead, in which case you would have...

I think you should be able to use return ... : Optional.empty(); based on pg 138 of Joshua Bloch's 'Efficient Java'

Some further information on this. I tried refreshing each query, updating repository configuration, adding a new query, restarting eclipse, deleting all queries and adding a new query. None of these...

You might be able to do this more quickly than you think. In Eclipse, if you use a Java Search for 'message' on Methods as shown then you will find...