familyTree | A family tree created using d3

It's not clear which module your initializeMaps() function is defined in, but that particular Google API requires that it be a global symbol so Google can find it when that script executes. And, it will have to be defined before the Google script executes too.

With ES6 modules, nothing in the script is automatically defined as globally available. So, unlike the older script files, top level variables in your script only have module scope and are not available globally. This is an important change with ES6 modules. You have to either export a symbol to make it available to other scripts or you have to explicitly make it global by assigning it to the window object (in the browser) like this:

Here is a way to solve your problem. The function familyTreeFilterChildrenByIndex checks the index of each element and also runs itself on any children.

This line is breaking your logic:

You can achieve that by creating an array of observables and passing it along recursively, then subscribing to it in getContext using forkJoin, as demonstrated below:

Yes - removing both of the **kwargs in wrapper_function will make it work in both 2.6.x and 2.7.x

It has to do with Ruby 2.7 deprecating automatic conversion from a hash to keyword arguments

Adding items is not reflected in the UI, because the source collection Person.Children doesn't implement INotifyCollectionChanged. Whenever you need dynamic collections, where add, remove or move operations should update the binding target, you should use the ObservableCollection, which implements INotifyCollectionChanged.

Similar applies to the Person.Name property. If you want a property's change to be reflected to the UI, then your view model must implement INotifyPropertyChanged and raise the INotifyPropertyChanged.PropertyChanged event whenever the binding source (the view model property) has changed.

Generally, when a class serves as a binding source for data binding, then this class must implement INotifyPropertyChanged (if this interface is not implemented, then the performance of data binding becomes very bad).
When the modification of a property should update the UI (binding.target) by invoking the data binding, then the modified property must raise the INotifyPropertyChanged.PropertyChanged event.
When the modification of a collection should update the UI (binding target) by invoking the data binding, then the modified collection must implement INotifyCollectionChanged and raise the INotifyCollectionChanged.CollectionChanged event. ObservableCollection provides a default implementation of INotifyCollectionChanged.

The following example follows the above rules. The changes made to the Person class should fix your issues. Changes to the data model will now be reflected in the TreeView:

Because you update state inside of forEach().

Maybe you should use .map and update state then at the end of check array.

This is the solution:

It working for fathers search, but I need it to iterate over all of the tree. When I added mothers root it core dumping again.