mabdullahsari

The error explicitly tells you what's wrong. But you're looking somewhere completely different.

null given

It means $event->user returns not a User model, but null. You'll have to check why that is the case.

I cannot tell what the exact issue is by looking at this piece of test code. But this is most likely the culprit:

assertSee escapes the passed argument by default (as of Laravel 6 I think?). This can mean two things:

1. You are not escaping your content properly in your blade views because you forgot to do so
2. You intentionally do not want to escape the content and in that case you can pass false as the second argument to assertSee.

"long HTML line of code" is very normal as it is trying to find that piece of information in your HTML response.

It's explained in the official docs: https://vuex.vuejs.org/guide/state.html

You have to map the state so Vue can detect changes and actually rerender your component.

computed: mapState([
  'sidebartoggle'
])

// in your template
<div id="wrapper" class="toggled" v-if="sidebartoggle">

No. You will have to use Telescope.

Yeah they are, my bad. Read the topic without drinking my morning coffee. Woops. Ignore me 🙈

https://github.com/spatie/browsershot

https://github.com/barryvdh/laravel-dompdf

https://github.com/barryvdh/laravel-snappy

findOrFail is not going to work because it matches the model's id by default.

Adjust your query:

Post::query()->where('slug', $slug)->firstOrFail();

You're probably using a PHP version < 7.4

Try this:

Model::query()
    ->with(['basket' => static function ($builder) {
        $builder->where('user_id', auth()->id());
    }])
    ->get();

You can simply store it in a textfield as is as long as you do not render the contents as raw html when using it.

So, don't do {!! !!} in case of Blade.

Same end result, different approaches.

You're probably using a PHP version < 7.4

Try this:

Model::query()
    ->with(['basket' => static function ($builder) {
        $builder->where('user_id', auth()->id());
    }])
    ->get();

That's default behaviour to protect your application from XSS attacks. You will need to explicitly say that you want to render HTML tags instead of plain text.

You'll need to do something like

<div v-html="data" />

I hope that you sanitize this data before saving it to your database.

findOrFail is not going to work because it matches the model's id by default.

Adjust your query:

Post::query()->where('slug', $slug)->firstOrFail();

That's default behaviour to protect your application from XSS attacks. You will need to explicitly say that you want to render HTML tags instead of plain text.

You'll need to do something like

<div v-html="data" />

I hope that you sanitize this data before saving it to your database.

No, it's valid. You can pass an array of relationships as well instead of plain string values. When using an array, you can modify the relationship queries individually.

Can you show us a snippet of what you're trying to achieve exactly?

You can pass in a Closure to modify the relation query:

Model::query()
    ->with(['basket' => fn ($builder) => $builder->where('user_id', auth()->id())])
    ->get();

CSRF is not a protection against spam, but for prevention regarding form submissions that happen against your will. e.g. Someone sends you a link, you click on it and they make a POST request in the background on that web page. CSRF is designed to prevent exactly that.

You will need to implement anti-spam mechanisms, such as https://github.com/spatie/laravel-honeypot Recaptcha is not infallible neither is the link I've provided. You'll need to examine what's happening.

CSRF is not a protection against spam, but for prevention regarding form submissions that happen against your will. e.g. Someone sends you a link, you click on it and they make a POST request in the background on that web page. CSRF is designed to prevent exactly that.

You will need to implement anti-spam mechanisms, such as https://github.com/spatie/laravel-honeypot Recaptcha is not infallible neither is the link I've provided. You'll need to examine what's happening.

No, that's not how ES Modules work. There is only a single source of truth and one declaration of the Form class. You can import it in 100 different locations and it will still be declared once, so there is no redundancy.

(Assuming you make use of a decent bundler like Webpack/Rollup)

collect(array_merge($arr1, $arr2))
  ->groupBy('name')
  ->values()
  ->map(fn ($person) => $person->reduce(fn ($acc, $cur) => $acc->merge($cur), collect()))
  ->each(static function ($person) {
      if (!$person->has('salary')) {
          $person->put('salary', 'unknown');
      }
  })
  ->toArray();

Read up on Collections:

https://laravel.com/docs/7.x/collections

@jenya Yes it is. You can just replace them with regular functions if you are below 7.4.

Also, can you mark as solved please? Thank you.

collect(array_merge($arr1, $arr2))
  ->groupBy('name')
  ->values()
  ->map(fn ($person) => $person->reduce(fn ($acc, $cur) => $acc->merge($cur), collect()))
  ->each(static function ($person) {
      if (!$person->has('salary')) {
          $person->put('salary', 'unknown');
      }
  })
  ->toArray();

Read up on Collections:

https://laravel.com/docs/7.x/collections

Well, since Laravel uses Symfony behind the scenes you don't need to require any package to crawl web pages inside your code. Take a look at: https://symfony.com/doc/current/components/dom_crawler.html

Add use Symfony\Component\DomCrawler\Crawler; inside your job and you're good to go.

So... what's the question here? 🙄

show is some piece of state so it belongs to data:

data() {
    return {
        show: true,
    };
}

hide after let's say a second:

mounted() {
    setTimeout(() => { this.show = false; }, 1000);
}

You should probably read up on the basics of Vue.

Too bad the talks were so short. Mohamed's talk was very interesting, but brief.

Have you even run the package migrations? It seems like you have not...

php artisan migrate

Switching to GraphQL won't make development magically faster. You will basically have to start over if you choose to do so.

Also, choosing a technology over another technology just because it's faster to developer with is an awfully bad idea.

Pipelines to the rescue: https://youtu.be/7XqEJO-wt7s

How you are going to implement it is up to you, but pipelines are a perfect candidate to introduce here. Will make it much more readable and maintainable.

Highly recommend you take a look at the video above (ignore the fact that it's L6).

show is some piece of state so it belongs to data:

data() {
    return {
        show: true,
    };
}

hide after let's say a second:

mounted() {
    setTimeout(() => { this.show = false; }, 1000);
}

You should probably read up on the basics of Vue.

You can use whatever you'd like to use. There is no best. I personally use mailgun.

The controller should only wire up different parts of your application and ideally not have any business logic inside of it.

It will become obvious as your application grows larger and larger.

Also testability plays a huge role.

Would you mind placing some back ticks around your exception stack trace? 😑

Why don't you put the styles inside the Vue component?

<style scoped>
...
</style>

You should place a setTimeout in the mounted lifecycle hook that toggles the show flag after an X amount of time so your component can actually fade out. Obviously, don't forget place a v-if="show" on your div.

Can you delimit your database values? What is actually saved as a separate row.

$table->id();
$table->foreignId('category_id')->constrained('categories')->cascadeOnDelete();
$table->foreignId('user_id')->constrained('users')->cascadeOnDelete()

You have to create the column before creating the foreign key. foreignId takes care of that.

The thing is, you have to decide whether you want to make use of event delegation or not. In your first example, there is no event delegation even if it looks like it because jQuery does a "foreach" behind the scenes on the selector you have provided.

In your conversion attempt, you are trying to make use of event delegation but it won't be straight forward without a few data attributes to determine the selection of the correct element.

Route before middleware is always run... well before any app/controller logic so everything seems alright. Can you show the accessor code?

You can use whereIn to pass along the array of ids:

Product::whereIn('id', $ids)->get()

The (unfortunate) simple answer is: you cannot.

You have 3 options:

• Use something in common rather than a driver specific functionality (e.g. there is a FIELD function is MySQL which you cannot use in SQLite, but you can mimic that function using CASE WHEN statements)
• Don't test that piece of code (you can use a phpunit group annotation and then mark that group as skipped)
• Implement 2 separate solutions each for a particular SQL grammar.

I'd personally go for option 1 if possible, and option 2 if not. 100% test coverage is not a must IMHO.

You can use whereIn to pass along the array of ids:

Product::whereIn('id', $ids)->get()

If you take a closer look, you can see that calling the request helper function without parameters returns the current request from IoC container:

if (is_null($key)) {
    return app('request');
}

That's why you see the whole request object. When you call it with a single parameter, it passes the call to the request instance:

 $value = app('request')->__get($key);

Thus returning the GET parameter bound to the current request.

Well, if you are going to use a dedicated resource collection class, then you do not have to use the static collection method which returns an AnonymousResourceCollection. At the moment, you are wrapping a collection inside another collection.

It's one or the other, not both.

Yeah okay my bad, your variables names are confusing.

Are you sure your connection string is correct? query returns false probably.

Place the setFetchMode above your query (select * from data).

You need to do the configuration before executing the query.

Well, if you are going to use a dedicated resource collection class, then you do not have to use the static collection method which returns an AnonymousResourceCollection. At the moment, you are wrapping a collection inside another collection.

It's one or the other, not both.

One way of solving is parsing the query string and extracting the client_id from it.

See https://www.php.net/manual/en/function.parse-str.php

Answering in order:

1. You have to go through the upgrade guide that gets released along with each major version (6 to 7 for example) and apply the needed breaking changes. You can also use automated upgrade systems such as JMac's Laravel Shift. Generally speaking for minor releases (7.x.x) for example) you do not have to do anything special as there shouldn't be anything breaking.

2. Yes and no. Reason is answered in point numero uno. There will be breaking changes with each major release. But this does not mean your project will break every single major update because it depends on what parts of the framework you are using. YMMV

3. If you are starting a fresh project, pick the latest release. No brainer. It will be the most mature and bug-free version of the framework.

4. When looking up tutorials, do not care about the minor release tags, so the "x" in version 7.x.x let's say. You could be following a tutorial made during Laravel 6's time which is still perfectly valid and viable. Things don't change that often when set in stone. Try looking up information as close to the current version you are using as possible. So don't go and read on Laravel 4 or early versions of 5.

5. Yes

Good luck!

@mokrani Remove that URL ASAP. You do not want to throw your API keys out in the public or else you may perfectly become a victim of abuse and get locked out of the service or worse get a spicy invoice thrown at you.

Coming to your question, you are using the API wrong that's why it rejects your call. Check the docs again.