Override isCollection for custom objects

Suggestion
Provide some way to use custom objects without treating them all as collections. There's a showCollectionWrapper property which sounds close, except it just hides the braces. It doesn't get rid of the extra line break, expand/contract functionality, etc. Maybe something like isCollection: false in customNodeDefinitions.

In our case, only "plain" Objects are collections, since we're parsing JSON (override some specific nodes with a custom object) and then passing in the result. So some logic like value.constructor === Object might also work. That probably wouldn't work in general, though.

Use case
We'd like to parse JSON using the lossless-json library, which puts numbers into a LosslessNumber type. The purpose is to show formatted JSON that doesn't modify the input at all. It doesn't translate 1.0000 into 1 or translate 123456789012345678901234567890 into 1.2345678901234568e+29, etc.

We can almost make this work with json-edit-react already, but it treats LosslessNumber as a collection.

Hey, thanks for the suggestion. I actually had to deal with this issue myself when I made a custom handler for Date objects: https://github.com/CarlosNZ/json-edit-react/tree/main/custom-component-library/components/DateObject

And yeah, I had the exact same issue -- the Date object was treated as a collection. I actually put a sneaky exception for "Date" objects into the isCollection check:

json-edit-react/src/helpers.ts

Lines 19 to 20 in dc278d2

    
           export const isCollection = (value: unknown): value is Record<string, unknown> | unknown[] => 
        
             value !== null && typeof value === 'object' && !(value instanceof Date)

But yeah, that's pretty specific for Dates, and as you've shown, there are other object types that we might want to not display as collections. I like your suggestion of an addition isCollection prop for the custom definitions. I'll try and add that in in the next week or so.

That would be fantastic, thanks! And there's no rush of course–if it takes longer than a week that's perfectly fine too. 😄 We've come up with a very silly workaround (which I won't admit publicly) in the meantime…

Okay, I've done this but not published a release yet, will release later this weekend.

We've come up with a very silly workaround (which I won't admit publicly) in the meantime

Ha, some ugly CSS hackery I'm guessing?

Hi @markdascher, this is done now and available in v1.27.0

I've called the prop renderCollectionAsValue, and it's documented here.

There are a couple of example implementations:

Date Object
"Enhanced" link (object with "url" and "text" fields, displayed as clickable string)

Hope that works well for you. If you think your custom "lossless number" component would be useful, you might want to contribute it to the Custom Component library :)

	export const isCollection = (value: unknown): value is Record<string, unknown> \| unknown[] =>
	value !== null && typeof value === 'object' && !(value instanceof Date)