comply | side ActiveRecord validations , all up in your HTML | Validation library

It look like passed variable $fromEmail ,$toEmilId ,$fromName, are empty.

Also make sure to trim $fromEmail ,$toEmilId .Even if your email contain space begining or at the end also you get error.

For example i have given space in $fromEmail then i get following error

You should start with below array. Notice that CustomerReferences is array of array. This will result in two CustomerReference in soap request.

But then I read in the Next.js documentation that fetch to internal API shouldn't happen inside the getServerSideProps()

You'd want to use the logic that's in your API route directly in getServerSideProps, rather than calling your internal API.

Here's a small refactor example that allows you to have logic from an API route reused in getServerSideProps.

Let's assume you have this simple API route.

Please follow the given steps to DEACTIVATE non-compliant APK (APK Version 25): Go to your Play Console. Select the app. Go to App bundle explorer. Select the non-compliant APK Version 25 at the top right dropdown menu, and make a note of which releases they are under. Go to the track with the policy issue. It will be one of these 4 pages: Internal / Closed / Open testing or Production. Near the top right of the page, click Create new release. (You may need to click Manage track first) If the release with the violating APK is in a draft state, discard the release. Add the policy compliant version of app bundles or APKs. Make sure the non-compliant version of app bundles or APKs is under the Not included section of this release. For further guidance, please see the "Not included (app bundles and APKs)" section in this Play Console Help article. To save any changes you make to your release, select Save. When you've finished preparing your release, select Review release. If the non-compliant APK is released to multiple tracks, repeat steps 5-9 in each track. Please note that after you submit an update to an existing app on your Play Console, it can take some time for your app to be processed for standard publishing on Google Play. To check your submission status, you may follow the steps below: Sign in to your Play Console. Select your app. On the left menu, select Release > Production or Testing (select the track(s) you have released) If you're an AdMob publisher, please contact the AdMob team to re-enable ad serving.

Laravel doesn't have official command to take db backup which you mentioned

You must use following package

https://spatie.be/docs/laravel-backup/v7/installation-and-setup

To know laravel default php artisan commands .You can run following command to defualt commands available in php artisan.

java-json-tools/json-schema-validator seems not to have been updated for some time. I'd probably pick one of the libraries listed here. These two seem to be most actively maintained: everit-org/json-schema and networknt/json-schema-validator.

networknt/json-schema-validator works with Jackson, which is one of the most popular JSON libraries in the Java world, so it should suit your needs. Here's a simple example of how you could validate a JSON object and print errors (I omitted error handling for the sake of simplicity):

This depends on whether you consider arg being None to be an error.

If it's a supported value that just means there's nothing to work on then checking for it and returning, as per your first solution, makes the most sense.

If it should never be None and someone passing that in is an error then just let the exception happen. Or, my personal choice, check it and throw an exception in __init__ to say the caller passed an invalid argument. Exceptions happening earlier (at the time the invalid thing happened) feels better than them happening later once a bunch of other things are going on and it's harder to figure out.

Go Wiki: Receiver Names:

The name of a method's receiver should be a reflection of its identity; often a one or two letter abbreviation of its type suffices (such as "c" or "cl" for "Client"). Don't use generic names such as "me", "this" or "self", identifiers typical of object-oriented languages that gives the method a special meaning. In Go, the receiver of a method is just another parameter and therefore, should be named accordingly. The name need not be as descriptive as that of a method argument, as its role is obvious and serves no documentary purpose. It can be very short as it will appear on almost every line of every method of the type; familiarity admits brevity. Be consistent, too: if you call the receiver "c" in one method, don't call it "cl" in another.

If you have a single method, it probably doesn't matter. If you have a type with many (maybe even dozens of methods), it does help if you use the same receiver name in all. It's much easier to read and understand.

Also if you want / have to copy some code from one method to another (refactoring), if the receiver name is the same, you can just do copy / paste and your done, you don't have to start editing the different names.

Also Dave Cheney: Practical Go: Real world advice for writing maintainable Go programs:

2.4. Use a consistent naming style

Another property of a good name is it should be predictable. The reader should be able to understand the use of a name when they encounter it for the first time. When they encounter a common name, they should be able to assume it has not changed meanings since the last time they saw it.

For example, if your code passes around a database handle, make sure each time the parameter appears, it has the same name. Rather than a combination of d *sql.DB, dbase *sql.DB, DB *sql.DB, and database *sql.DB, instead consolidate on something like;

The cookies used for Firebase are specifically for Authentication reasons only, Firebase doesn't track personal information or data but rather stores a randomized Javascript Web Token to re-authenticate a user when your app gets refreshed or reloaded.

Additional client-side data is used for caching the database to increase read performance but doesn't expose or track a user by any means either.