kondo | Cleans dependencies and build artifacts from your projects | DevOps library

try pd.json_normalize() with the max_level argument.

It looks like it is because all the sections are depending on the same state. Thus, once that state changes, all the sections are being affected. How I would approach this would be to have state hold the current hovered section. E.g.

The top level Makefile that is generated by cmake has .NOPARALLEL:. It prevents parallel build. So even if I execute make -j2 a b, target a and b build sequentially.

cmake also generates CMakeFiles/Makefile2. It is used as follows from the top level Makefile:

From the clj-kondo documentation:

Sometimes vars are introduced by executing macros, e.g. when using HugSQL's def-db-fns. You can suppress warnings about these vars by using declare. Example:

The quotes serve a purpose here so you shouldn't be removing them haphazardly. The quotes prevent columns from breaking when they need to contain text that can also contain the delimiter. Like "Foo, bar, baz" for example. Removing the quotes turns this one column into 3 columns, which is obviously wrong.

Though, if you did want to remove them str_replace would certainly not be the way to go, because the quotes can be escaped to be literals inside the column. For example, using str_replace on this column: "He said \"this is crazy\", and left." would strip literals from the column value.

Instead you should load the CSV data with fgetcsv() or str_getcsv() and rebuild the CSV without the quotes like so...

It uses the previously defined BookRepository in order to insert three Book records. This allows for verifying that the service works as expected.

Without it, testing the service with curl in Step 7 would not return a result. Though the author could have organized the tests such that the updates are executed first.

It is not a crucial step in developing services, but it shows that there is an easy way to interact with Spring components.

You should not fetch your data values by ID because it's not possible to have more than one of the same ID elements.

Since you're using jquery anyway, use $('form').serialize() or $('form').serializeArray() for array output to fetch all the form inputs and it's values. You will have to wrap those inputs in a form element before you do this though.

Or as suggested above, loop over the elements manually and get the values like that.

All sorted

According to the "mailing list" example from these PHPMailer examples, your general approach seems to be similar to the one given in the example. If you think sending out 50-100 emails in this process will be unacceptably slow for the user—at least for the user interface (UI) response time after the sending process has started, the following topics are a few possibilities for approaching your situation.

Like you mentioned, it would be possible to store your "to-be-sent" mailing data into a database table. This gives you the option to schedule a cron job to run a different script to actually mail out these "to-be-sent" emails without getting in the way of the original user's experience.

The downside here, however, might have to do with the added complexity of letting the user know if a mailing has been successful or not.

Though PHP might not be the easiest language in which to use threads, it might be time to look into working with threads in order to free up your UI when a time-intensive task like this needs to be performed.

Basically, you would likely want to set up a thread for sending messages. This way, when a user goes to send a bunch of mailings, the actual sending task would be running in a thread apart from your UI, so the user would not necessarily have to wait for the task to complete in order to move on in your app. This article might get you started with threads in PHP, should you decide to try this route.

Like you also mentioned, a message queue could be used to send a task for later actions to be performed, but if your general use case does not go beyond something like 50-100 emails at a time, using a message queue might be more complicated than necessary for your particular situation.

However, these approaches are more theoretical and may be more helpful in other contexts.

For this type of mailing in PHP, you may want to try looking at mail queues such as emailqueue or Mail_Queue (as mentioned in this post), though I don't know if these tools are still up to date.

Finally, in response to your question about Bcc, some people seem to think that using Bcc might send mail in a faster way, but you might want to try using Bcc versus not using Bcc in order to test that out for yourself.