Christopher Currie
Christopher Currie
Workaround: it looks like this equivalent succeeds: ```js let fn = () => { let obj = ({ foo: 1, bar: 2 }); } ```
Looks like it might be specific to collections types. This should be doable without much trouble, I'll look at it for 2.6.2.
Can you provide an example of the case class that is causing problems?
No one has done any work to explicitly support this use case in the module; if it doesn't work, it's because something in the Scala specific logic is suppressing what...
Sounds good. FWIW, 2.6.0 was unfortunately released incorrectly, and Maven doesn't have a way for us to mark the release as invalid. For the Scala module only, 2.6.0-1 is available...
Just following up, I haven't had time to look at the filtering issue, but I am also concerned about the property naming issue you mentioned. If 2.6.1 isn't naming properties...
This is the correct place for this issue. The Scala module will need to add support for `@JsonManagedReference`, which was a feature I wasn't aware of. We'll see if can...
None of the Scala collections implement any of the Java interfaces. If databind could use the "collection-like" and "map-like" properties, rather than `instanceof` checks, this might work for Scala collections...
Let me see if understand: the code works fine if you run it using scala on the command line, but not within the REPL?
Cool, thanks. The REPL has odd behaviors sometimes but I try and support it to the greatest extent possible. I'll take a look and see what can be done.