You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside func (n *sortNode) Explain() (map[string]interface{}, error) function in sort.go file, we have to skip over n.ordering's empty elements using the IsEmpty() method.
Investigate why ordering is populated by the empties, and remove the use of IsEmpty().
The text was updated successfully, but these errors were encountered:
- Resolves: #589
- Description: Hunch mentioned in last week's meeting was correct, it was indeed a `make` where it would populate the array with empties and then append being called on top of it. Also removed the function `IsEmpty()`, we used to check for empty elements previously which was introduced in #481.
- Resolves: sourcenetwork#589
- Description: Hunch mentioned in last week's meeting was correct, it was indeed a `make` where it would populate the array with empties and then append being called on top of it. Also removed the function `IsEmpty()`, we used to check for empty elements previously which was introduced in sourcenetwork#481.
Discovered as part of #558.
Inside
func (n *sortNode) Explain() (map[string]interface{}, error)
function in sort.go file, we have to skip overn.ordering
's empty elements using theIsEmpty()
method.Investigate why
ordering
is populated by the empties, and remove the use ofIsEmpty()
.The text was updated successfully, but these errors were encountered: