Databases
StackOverflow2013
Postsdbo
POPHP - Avoiding nested if statements - cleaner way to code this
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP - Avoiding nested if statements - cleaner way to code this
    primarykey
    data
    text
    <p>Assume that I am creating a registration form. I have code like the below and it is hard to manage because of all the nested if statements.</p> <p>I want to know the cleanest and easiest to follow way to write code that functions similarly to what I have below.</p> <p><strong>EDIT</strong>: People have told me that I can move the empty($_POST['email']) to the validation functions. I can't do that because I need to know 1) whether user has posted data or not, and 2) whether the data user posted is valid. </p> <p>For example, when the user first goes to the registration page, they have not posted any data so $_POST['email'] will generate PHP warnings because they don't exist. That's why I check whether data has been posted before I validate.</p> <p>Does this make sense?</p> <pre><code>function validate_email($str) { $str = trim(strtolower($str)); if(!filter_var($str, FILTER_VALIDATE_EMAIL)) { return false; } else { return $str; } } function validate_password($str) { $str = trim($str); if(strlen($str) &lt; 5 || strlen($str) &gt; 70) { return false; } else { return $str; } } $email = false; $password = false; $errorMessage = false; if(!empty($_POST['email'])) { $email = validate_email($_POST['email']); if($email) { if(!empty($_POST['password'])) { $password = validate_password($_POST['password']); if($password) { createNewUser($email,$password); } else { $errorMessage = "The password is not valid"; } } else { $errorMessage = "The password is not valid"; } } else { $errorMessage = "Email address is invalid"; } } else { $errorMessage = "Email address is invalid"; } if($errorMessage) echo $errorMessage; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USfun_programming
    1. USfun_programming
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPHP - Avoiding nested if statements - cleaner way to code this
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTheres nothing really wrong with that, there may be a neater way but it probably won't be as fast
      singulars
      1. POPHP - Avoiding nested if statements - cleaner way to code this
      1. USAdam
    2. COit's not like speed is any issue with such code. The only real concern here is readibility.
      singulars
      1. POPHP - Avoiding nested if statements - cleaner way to code this
      1. USFemaref
    3. CO@AdamTester Code being maintainable has much higher priority then a little gain in speed. Which probably will be not noticable.
      singulars
      1. POPHP - Avoiding nested if statements - cleaner way to code this
      1. USBart
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload