formHandler | practice with forms in react | Form library

While you can't go from child to parent (bottom up), you can always go top down from parent to child using state propagation. Declare a state variable and it's change handler inside FormHandler.js and pass it as a prop to the Custom Form Component. Let's say you need 1 extra field as in CustomForm1. The code should look something like this:

Inside FormHandler.js (Assuming you are using functional components)

I think the issue is caused by passing "Product.Supplier.Name" as the string value into your FormGroupParams object for the partial model. Instead you need to pass the actual value of the Product.Supplier.Name property from the model.

Something like this maybe:

Ciao, you could try this:

I think I see what you're trying to do, when you make the request to the server it will make a new Laravel instance to handle the request, and thus any objects (i.e. the controller object that you are trying to attach the request inputs to) will be fresh, so new requests won't have access to $this->result, as it is a fresh instance of the controller. The only way to access it would be to store it in the database and then access to again, or send all the data from all the forms for each request. It's simply not possible (nor would you want it to be) to access data from a different request.

You can look into using Redis to cache data in memory between requests which is probably the most common solution to this kind of problem.

JSONParser is missing.

In views.py

Anytime you have a button of type "submit" in a form (or one that does not specifically say that its type is NOT "submit" by specifying a type of "button"), the browser is going to view its click as the user wanting to submit the form. So the answer for your first question is simply to add type="button" to your continue button, instead of "submit".

You wrote a form handler override that tried to prevent the above, I don't see an obvious reason why it wasn't preventing it, actually.

Secondly, you seem to be trying to call your submit function by referencing this.state.formFields. However that does not exist in your state. When you update your inputs, you are using this function:

You can have access to it by serving It's content as express static.

To answer your 1st question: If it's safe, depends on what you intend to do with it, but since you want to save this into the database, at the moment, it's not safe. You answered your question yourself with the 3rd question. Always use prepared statements.

I'd also say it's not that smart. Sure, it's smart in a way, that you don't need to care about any new variables etc. but what happens if

• You are re-designing your database? Then, you don't know where some fields are used
• A user simply adds more fields (or removes fields) from the POST request (by changing the form or manually sending the request?) Then everything will fail, because you will be trying to insert unknown fields into the database
• When refactoring, you can't search for usages in your IDE of automaticaly generated variables. (That's also why I'm no fan of calling methods by string concateation or similar)

Simply said: I'd avoid "magic" for creating variables, methods or anything else. Don't think about what's easy to program. Think about what's easy to maintain and easy to read later! No one will know what happens in this code just by reading it, and that should always be #1 priority

To answer your 2nd question: String is not more or less insecure than any other data type. Passwords should always be encrypted (I'm not actively developing PHP anymore, so don't know if this is the current standard but take a look at: https://www.php.net/manual/de/function.password-hash.php)

What I like to do for what you're trying to achieve is serialization/deserialization

The symfony framework has a nice graphic for this

Source: https://symfony.com/doc/current/components/serializer.html

So, since you already have an array, for you it would be denomrlization. You could write a denormlalizer which does nothing else than to convert the array to the model.

I don't know if this is already too advanced but you could take a look at

• https://github.com/symfony/serializer
• https://github.com/schmittjoh/serializer (although i'm not the biggest fan of jms)

Try to refactor your code to functional style: