bugsysha

Can you mark best answer?

You are overriding value.

Have no idea what your code is doing but try replacing with one of following

$myPpe[] = array_values($ppeWorn);

Or

$myPpe = array_merge($myPpe, $ppeWorn);

You can check out https://course.testdrivenlaravel.com/ and https://www.youtube.com/watch?v=MdApmmK71WM

Sometimes I have to change test code after change product code.

You should do the other way around just to build a habit of proper TDD workflow.

In reality, if the requirements change then the feature tests should be changed too. As a result, it should need product code to be changed. It cannot avoid brittle code anyway.

True, you can not avoid changing business requirements. You can write tests in such a way that it is not too coupled to the implementation. But as you said, sometimes it can not be avoided for a test to fail. Like you were sending notifications before, but now you do not. Or some events were not dispatched and now they are.

So, Is it necessary to be concerned about brittle code when doing TDD?

Yes, you definitely need to be concerned about brittle tests, just don't worry about that too much. The experience will come with practice. A lot of practice.

You can create a middleware and restrict access based on IP and/or email.

I assume videos are directly uploaded to Vimeo.

I only use model approach. Check this out https://youtu.be/dfgtKb-VpRk

And Adam Wathan is a very practical guy who values productivity so if someone with his level of experience takes that approach then I don't see a reason why someone would skip on the opportunity to create a single listener class for already existing event and do himself a favor down the road. As Michael Jordan says in that Nike commercial, "or maybe your just making excuses" to write crappy code.

If creating one class is overkill then I don't know what to say. Jeffrey Way once said that only inexperienced software engineers are reluctant to create new classes.

If you Google for a term like scalable software you will see that the definition is something like "maintaining performance during a huge increase in load".

What if you need to log to some external CRM also and request lasts for 250ms. Then you need to send an email and that also takes another 250ms. And so on, add another 5-10 services that you need to notify, or things that need to happen during some event like login. Your solution will become a bottleneck.

In that case, scalability will not be possible. Not to mention that you are violating the core principles of good software architecture.

I think that you are missing. I do not know any other way to create truly scalable, decoupled and polymorphic architecture without events. In my mind it is the only way, but maybe I'm just too old 🤣

Have you tried listening to \Illuminate\Auth\Events\Login event?

Still confused why do you need variable chunking. Is there a screenshot or something that can help visualize the problem?

In my mind that does not make sense. Having different sizes chunks is something I've never reached for. Why would you need such a thing?

Did you install all dev dependencies?

I'm using docker. PhpStorm is running them for me. Just had to specify a remote interpreter.

Install new Laravel app and try the same. That way you'll figure out if it is due to your OS or your Laravel app.

Is this something can happen?

No. Emails are unique. Either your user was completely hacked and does not have any access to own online accounts or it is the same person you have in your system. So that case you've described does not make sense.

Is this something can happen?

No. Emails are unique. Either your user was completely hacked and does not have any access to own online accounts or it is the same person you have in your system. So that case you've described does not make sense.

And what happens when you run that command from terminal from the Laravel root folder?

What's happening here?

Just a simple query SELECT * FROM users WHERE email = '[email protected]' LIMIT 1.

Is this secure against a malicious user?

Yes.

Where did you find an example of such syntax? I do not recall seeing it in the docs. You have to use terminal commands to generate a command php artisan make:command NameOfTheCommand and then edit the generated file, and then in Kernel you can schedule it.

Just add some column and fill it when creating the record based on previous records for that specific user.

https://laracasts.com/search?refinement=type&name=episode

@stonecold first of all congrats on using search. That is powerful feature that no one uses on forums. Everybody just creates new discussion with answers under their nose.

Can you describe in bit more detail your problem?

No. Just have users table with type column.

Just put everything you did in PHP into Laravel controller and start refactoring.

@jank if that is solution, please mark it as best answer. Thanks.

Caleb is talking there about gotchas that you should be aware. Probably you can find all those on internet.

1. Create migrations
2. Run php artisan migrate on your local machine
3. Copy data from migrations table as SQL insert statement
4. Execute that statement on production
5. Deploy code with migrations on production

That way no migrations will be executed on production since it will have them in migrations table.

@celotrovi have you watched that video that I've posted in my first reply in this thread? Maybe that can give you better idea of what you are doing wrong.

Laravel is PHP, so what you can do in PHP you can do in Laravel.

You can create some function for that to avoid repetition.

You have to loop over $leftJoins and add statements to the builder.

$builder = DB::table($table);

foreach($leftJoins as $leftJoin) {
	$builder->leftJoin(...$jeftJoin);
}

$results = $builder->get();

Create an action in Vuex that you call on a scroll, and push result to the state property that contains your data.

Why do you need composite index to be your primary key? I think that you must provide string, not array.

If I understand the question, then the answer is, Yes.

https://www.php.net/manual/en/book.ldap.php

All best.

Not sure how it is a generalized comment? It is very specific. I wanted to embed those videos for my project and had same issue as I have here on Laracasts with Vimeo as a provider.

@tray2 great article. I think I've been using it a bit longer. I would say from 2017-2018, but maybe I'm mistaking since I've read it in some article also.

@tray2 I didn't want to mention data providers since people do not use them in an organized way. But I see you've nailed that one same as me with keys and values.

Whenever I use my old laptop to watch Laracasts videos it spins up the fans.

No need for kissing. Just remember that commands and jobs resolve dependencies from the handle method.

I know that was an issue years ago, and then an article showed up explaining how to upload longer videos, but I have no idea if that is still an issue.

The only issue I've came across was that you can not upload more than 100 videos per day.

Commands resolve dependencies type hinted in the handle method, not in the constructor. Try that.

For me, Vimeo is not good enough. Especially when users have older laptops, when they watch a video it spins up the fans like crazy. Not sure if there is anything better. I've ended up using YouTube.

Commands resolve dependencies type hinted in the handle method, not in the constructor. Try that.

$bindings = $builder->getBindings();

$builder = Vacancy::statusId($request->query('status'))
            ->sellerId($request->query('seller'))
            ->categoryId($request->query('category'))
            ->locationId($selectedLocationId);

$query = $builder->toSql();

$products = $builder->get();