demeter | Demeter is a tool for scraping the calibre web ui | Media library

You could simply copy the required rows to another dataframe,

This seems to be the same Problem I had Nested deserialisation fails with "This field is required"

Make sure to use the APITest which sends the request JSON encoded.

To fix it I changed my testcase to use the APIClient provided by DRF:

You are right, there are some drawbacks, if you want just a data-binding, I would suggest to use Combine instead, since no 3rd party libraries need, you have it already. RxSwift is a very powerful tool when you use it as a part of language, not just for data binding.

Some of suggestions from my experience working with RxSwift:

1. Try to make VMs as a structs, not classes.
2. Avoid having DisposeBag in your VM, rather make VC subscribe to everything(much better for avoiding memory leaks).
3. Make its own VMs for subview, cells, child VC, and not shared ones.

Since your VC is a dispatch centre, I would make a separate VM for your content view and make a communication between ContentView VM and ViewController VM through your controller.

The 403 Forbidden is related to the user or service account who is deploying the function. You will need to have at least the roles/cloudfunctions.developer in order to be able to deploy a Cloud Function.

Also, you must also assign the user the Service Account User IAM role (roles/iam.serviceAccountUser) on the Cloud Functions Runtime service account.

Ref: https://cloud.google.com/functions/docs/reference/iam/roles#additional-configuration

One way would be to repeat the rows of df by the lengths of the extracted values.

I think you grok the idea but I'm not sure if your example really makes sense. In the context of a board game, it's difficult for the Board to not be concerned with the possible movements! (So applying Demeter here would not make sense as possible the Board already has access to the Movement class).

Don't mock the JPA API, just write integration tests with proper test data and execute the real queries against real data to see if everything works. Projects like testcontainers make it very easy to get started.

I think a lot of what you did, specifically around data wrangling, was not necessary, especially since you called d3.hierarchy() and d3.cluster() afterwards. I've replaced this with d3.stratify (which deals with hierarchical data that is not yet in the right format).

I've also replaced d3.cluster with d3.tree() because it was unclear to me why you'd want to use d3.cluster here. Your data has multiple parents, multiple roots and even floating nodes, and d3 is not meant to deal with that. My workaround has been to attach pseudonodes to every level, so as to make sure that there is only one node and that all nodes are at the right level at all times. To make sure the links were drawn correctly, I've written a custom getLinks function, that can deal with multiple parents.

I've also written a custom link generator that draws the links somewhat in the way that you want them. d3 doesn't offer much of flexibility here, but you can use the source code for inspiration.

Edit

I've changed the logic to be more focused on which "partners" got a child, so both links to the same child are on the same level - like in your picture. I've also drawn the nodes based on how many partners they have, and have given every link an offset so the lines are more distinct.

I've sorted the nodes so that the real pro-creators are at the top (Zeus), which gives a more balanced and less crowded view.