Yup: What exactly does noSortEdges do?

[cjones26]

I recently had two fields--"a" and "b"-- if a user entered a value into either "a" or "b" then both fields should be made mandatory. I was unable to get this working until I added both of the values to the "noSortEdges" array param as shown below:

object.shape(fields: object, noSortEdges?: Array<[string, string]>): Schema

I can find zero documentation on what this parameters actually _does_, it did seem to fix my cyclical dependency issue, though I have absolutely no idea why.

Anyone?

Thanks!

-CJ

[jquense]

It's a ugly escape hatch for dealing with cyclical dependencies. Generally fields are topographically sorted so they can be resolved in the correct order, i.e. field A resolves before field B if field B depends on it.

In some cases tho the order doesn't matter, because the dependency is purely for the sake of validation, which all happen after all casting is done. In those cases it's _fine_ if there are cycles between fields, and you can manually opt out of the ordering, if you are sure that it's not needed. The reason it's not documented is that its a bad API and really easy to shoot one's self in the foot with it. I've had dreams of adding a real API but it's a bit tricky b/c it would require determining if a dependency is validation only, at schema construction, something that isn't really possible.

[cjones26]

Got it--thank you!