rembrandt | A library for generating and storing syntax-highlighted text | Code Inspection library

There are a few ways to do this:

1. If you just want to use the inbuilt python string functions, then you could do it by first splitting everything on the basis of / and then stripping the common part across all URL's.

Combine the two lists of images and titles one by one.
For the iteration, unpack the two variables of the respective tuple.

You can use numpy to solve this:

Using parse_dates / date_parser looks a bit complicated for me, unless you want to generalise your import on many date columns. I think you have more control with converters parameter, where you can fit dateclean() function. You can also experiment with dtype parameter.

The problem with original dateclean() function is that it fails on "" value, because int("") raises ValueError. Pandas seem to resort to standard import when it encounters this problem, but it will fail explicitly with converters.

Below is the code to demonstrate a fix:

If you treat the artist's name as a parameter, then you shouldn't hardcode the route like you're doing it, but rely on route params:

What appears to be happening for you is that the data-toggle="modal" anchor element (with (click)="getArtworkDetail(artwork.id)") triggers the modal before the request for the artwork detail has completed.

Try these two things:

1. Remove the *ngIf="details" directive from the modal div. Instead, put *ngIf="details" on an inner element -- perhaps the .modal-body element or a container div inside of that element.
   • This will allow the thumbnail button to trigger the modal without having to wait for the artwork detail to load
2. Add this.details = null; back to getArtworkDetail as the first line of the function. This will clear out all of the old detail information as the new detail information is loading.

You will likely want to display a spinner until that request has completed at some point. In that case, you can use your *ngIf="details" directive to provide a spinner while the details value is null: *ngIf="details; else spinner".

The single-threaded nature that your colleague referred to is actually with regards to JavaScript, rather than TypeScript, since TypeScript gets compiled to JavaScript before being executed. JavaScript effectively has runs as a single-threaded event-loop (although this is not guaranteed), but certain tasks triggered from these events may occur asynchronously. One such asynchronous task is an XMLHttpRequest. Since this occurs asynchronously, the script does not have to wait for it to complete before attempting to display the modal, which is where your problem seems to lie.