inspiring | Alternative inspiring quotes for Laravel

The Person component takes person as a prop. In the error message, it shows you're incorrectly assigning props to the Person component. It should be this:

What you are experiencing is called "collapsing margins". Example: If there's an h2 as the first child element inside a div, and the div has no margins, the top margin of the h2 will "go outside the div" at the top - h1, h2 etc. tags have a default margins in practically all browsers (which is a browser setting). To prevent that, you can define all margins for according elements as zero, like I did below with

You can't use batch_size with model.fit() when using a tf.data.Dataset. Instead use tf.data.Dataset.batch(). You'll have to change your code as follows for it to work.

For dates, I recommend a more robust and flexible solution. Using date-fns' format.

You can find an example here: https://github.com/date-fns/date-fns/issues/946#issuecomment-452766765

But using something like format(new Date(), "hh:mmaaaaa'm'") should be good enough, and flexible on top of it. Also, unlike Momentjs, this lib is optimized and does the job well.

Is your column Ratings string or list of dictionaries? If string, you can apply ast.literal_eval and then explode the column (if list of dictionaries, you can omit the literal_eval step):

There are misisng values so first replace them by DataFrame.fillna and then test if match values between columns by not in statement in DataFrame.apply with axis=1 and filter in boolean indexing:

From the wiki :

The 404 or Not Found error message is a HTTP standard response code indicating that the client was able to communicate with the server, but the server could not find what was requested. so, your code is OK, but server cannot find resource you are looking for. Double check if your url is correct.

You need to check if you're entering the correct url for the post request.

I'm assuming that you have a solid reason for not using express or equivalent webserver framework, and although I would strongly recommend using such a tool for all but the smallest of use-cases, I'll still attempt to point you in the right direction given your current setup.

You have no route handler for "/": The reasons the server hangs when you go to localhost:3000 is that the request handler function doesn't have any behaviour for "GET /". You should see your response if you instead visit localhost:3000/cards

Serving the card by id: The best approach (given the technical constraints) to serve the card by id is something like this (rest of code ommited for brevity):

It returns the last passed project, with the timestamp as a plain Javascript object instead of a Timestamp type

I do not expect this behaviour from the router and would like to understand what is happening.

What's going on is that the state is being serialized and then deserialized, which means it's being converted to a JSON string representation and back. You will preserve any properties but the your methods.

The docs should probably be more explicit about this but you should not store anything that is not serializable. Under the hood React Router DOM uses the browser's History API and those docs make it more clear.

• as in typescript is an assertion. It how you tell the compiler "use this type even though it's not really this type". When you have something that really is the type then do not use as. Instead apply a type to the variable: const project: IFirebaseProject = {

• Your getProjectId function to get an id from a URL is not necessary because React Router can do this already! Use the useParams hook.

• Don't duplicate props in state. You always want a "single source of truth".

I played with your code a lot because at first I thought that you weren't loading the project at all when the page was accessed directly. I later realized that you were but by then I'd already rewritten everything!

Every URL on your site needs to be able to load on its own regardless of how it was accessed so you need some mechanism to load the appropriate project data from just an id. In order to minimize fetching you can store the projects in the state of the shared parent App, in a React context, or through a global state like Redux. Firestore has some built-in caching mechanisms that I am not too familiar with.

Since right now you are using dummy placeholder data, you want to build a way to access the data that you can later replace your real way. I am creating a hook useProject that takes the id and returns the project. Later on just replace that hook with a better one!