genealogy | Visualizing family trees | Data Visualization library

first() returns null when a record is not found, you just need to check for null before using the variable.

You can use optional(..) to avoid null issues or the null function accessor $var?->function(…)

The problem in your controller is because you first try to find the user matching $headuser_id with the code:

Just pass people state as a props in your table component like this.

Your seperate table component:

I really appreciate the precision in design which ES2015 and above permit. Running eslint over the ES2015 versions of my code has detected several dubious design issues.

To support migrating one application at a time I implemented a second directory containing ES2015 versions of all of the JavaScript files which are included by individual pages to obtain common services. Fortunately I had already isolated all of those scripts in their own folder of the web site, jscripts. So I created a parallel folder jscripts6 in which all of the ES2015 versions of these support files are stored.

So the ES3 version of a page uses a template which includes library routines from folder jscripts, for example:

• I think that in your script, Blob is returned from Google Apps Script to Javascript using google.script.run. Unfortunately, in the current stage, Blob data cannot be directly sent from from Google Apps Script to Javascript. I think that this might be the reason of your issue.

In this case, I would like to propose to directly create the data URL at the Google Apps Script side. When your script is modified, it becomes as follows.

The need to update multiple aggregates in a single transaction is a sign that aggregate boundaries are wrong. Because an aggregate is responsible for protecting a transaction boundary by definition. And a single event corresponds to a single transaction.

Let's consider how this case is handled in a non-computer world. The business domain is well designed there. Sharpened through centuries to be as robust and simple as it gets.

The point of decision is not a person or a family. It is the church. Metric book is the aggregate. When a priest makes up a decision, he writes it down into a metric book. Everything else - person's documents, genealogy, list of person's facts - are mere read models in the registration bounded context.

They can be aggregates in other bounded contexts. And some service may listen to registration events and update relevant entities after the original transaction is completed and event is written. Eventually.

Here's a class I wrote which should do what you need:

Just use selectionitem instead of selectionitem.value

Managed to get this working myself, after a bunch of trial-and-error. Wasn't quite as difficult as I assumed it would be, DOMDocument actually takes care of some of the removal logic itself.

Django has a Client [Django-doc] that allows you to inspect the context. Note that normally the context is not exported in the HTTP response, but it is patched here to allow that for testing: