please i need explanation i dont what the variable is result is doing in the function

Checks if Email is valid, why not consult php manual ?

WallStreetfx:
please i need explanation i dont what the variable is result is doing in the function

That is filter_var() function, it is used to check or validate input based on the choice of algorithm you choose.

FILTER_VALIDATE_EMAIL is a constant that will choose algorithm for validating email

Why would anyone want to validate emails from the backend? Unless for educational purposes, all data are being validated at the frontend to save time

fhranchez:
Why would anyone want to validate emails from the backend? Unless for educational purposes, all data are being validated at the frontend to save time

JS can be disabled, Backend is your best point to secure bad input

fhranchez:
Why would anyone want to validate emails from the backend? Unless for educational purposes, all data are being validated at the frontend to save time

Every good programmer validates at the backend.

qtguru:
Checks if Email is valid, why not consult php manual ?

Baba, let's link up on Slack. There's a possible Laravel/Django gig from Malta

fhranchez:
Why would anyone want to validate emails from the backend? Unless for educational purposes, all data are being validated at the frontend to save time

First rule of web development never trust an input from a user

Unless you are coding for yourself , always validate every input at backend else ....,

fhranchez:
Why would anyone want to validate emails from the backend? Unless for educational purposes, all data are being validated at the frontend to save time

never trust the USER.

I suggest frontEnd + backEnd Validations. That way, the frontEnd validation spots and informs the user of potential errors so as to save time of going back & fort. The backEnd validation is a must and should never be skipped.

Moreover that code above is unnecessarily long. Shouldn't exceed 4 lines, and with ternary operator, should be just a single line. Still recall when PHP was the only language I spoke. Kai

bassdow:


never trust the USER.

I suggest frontEnd + backEnd Validations. That way, the frontEnd validation spots and informs the user of potential errors so as to save time of going back & fort. The backEnd validation is a must and should never be skipped.

Moreover that code above is unnecessarily long. Shouldn't exceed 4 lines, and with ternary operator, should be just a single line. Still recall when PHP was the only language I spoke. Kai

you mean data sanitization?

Wow, so ya'll devs can't differentiate between data validation and and data sanitization?

fhranchez:
you mean data sanitization?

Sanitizing differs from Validation.

bassdow:


Sanitizing differs from Validation.

thank you, not trusting the user is sanitizing the input, but guiding the user to make valid inputs is validation. So, why should i do that in the backend again, if not for time wasting

fhranchez:
thank you, not trusting the user is sanitizing the input, but guiding the user to make valid inputs is validation. So, why should i do that in the backend again, if not for time wasting

1. Javascript can be disabled and your validation rules would not even run and you would run into big problems by working with wrong input (database errors, huge logical errors).

2. Anything on the front end can y manipulated by the user. 98% of users would not know how to do this, but it can be done, so if you are using user input without validation and sanitation, you are setting yourself up for big headaches.

An example for context, let's say you are building a grants app that allows users to request grants from the government. But each user can request a maximum of NGN 500,000 only. And you create a validation function on the frontend that checks the input and ensures the value is below the limit before submitting the form.

If I decide javascript from my browser, then your validation function will never run and I successfully request for a grant of NGN 10,000,000 without any issues.

So even if you validate on the frontend, you should always always validate on the backend.

Never ever trust any input from the end user.

404Dev:


1. Javascript can be disabled and your validation rules would not even run and you would run into big problems by working with wrong input (database errors, huge logical errors).

2. Anything on the front end can y manipulated by the user. 98% of users would not know how to do this, but it can be done, so if you are using user input without validation and sanitation, you are setting yourself up for big headaches.

An example for context, let's say you are building a grants app that allows users to request grants from the government. But each user can request a maximum of NGN 500,000 only. And you create a validation function on the frontend that checks the input and ensures the value is below the limit before submitting the form.

If I decide javascript from my browser, then your validation function will never run and I successfully request for a grant of NGN 10,000,000 without any issues.

So even if you validate on the frontend, you should always always validate on the backend.

Never ever trust any input from the end user.

hmm, nice one

fhranchez:
Wow, so ya'll devs can't differentiate between data validation and and data sanitization?

So you don’t validate inputs on your backend?

Every garbage that can bypass the frontend wham…straight into your database?

Wonderment.