finduser | Find usernames across over 75 social networks | Networking library

I would do it that way

I solved this with Joffrey's reply, I used this format of config file

Use findUsers instead of findUser.

Don't include a filter, and it'll use the default filter of finding all users:

The core of the problem here is that Success and Notifier are both structurally the same, so TypeScript thinks that if the following if statement has a chance of returning true for one of those classes, it would return true for both:

if(result.isFailure())

Hence, the result value type after this block is automatically inferred as never. I have created an example to illustrate this here.

This problem can easily be fixed by introducing a unique field/method within one of the two classes or alternatively adding a private field/method.

The explanation above will fix the issue you are having and can be used to describe the behaviour of the if(result.isFailure()) statement. However, if(result.isSuccess()) on the other hand still appears to work with your original code. The reason for that is because you have introduced dynamicity in the order of how the nested generic types are assigned to the extending classes:

extends ResultAbstract vs extends ResultAbstract

Given the above, the classes can be considered to be different, however TypeScript will still think that Success and Notifier are the same as the is predicates tell it that Success can be Notifier (via the isFailure method) and Notifier can be Success (via the isSuccess method). Hence, all you need to do is remove either the isSuccess or the isFailure method and the code will start to work as it will tell TypeScript that it can only be one. Because your code only uses two classes, this would be the most suitable solution.

created() is totally fine with Vue but usually you do use fetch() and asyncData() hooks in Nuxt.
Here is the basic idea using JSONplaceholder's API.

Here is a possible /pages/index.vue

1. You forgot to use $this in Authentication::__construct() and Authentication::login() as well. If you want to refer to an object's property from within its own method you need to use $this. Otherwise it refers to a local variable within the method if it exists or to an undefined variable. The latter also generates a notice except if this is an assignment to the formerly undefined variable.

   So in these methods you need to write $this->AuthenticationModel instead of $AuthenticationModel.

2. In the Authentication::login() method you are also referring to an array's key without defining the variable itself as an array: $data['Uname'] = "testuser";...

   $data should be defined as an array like $data = []; or $data = array(); before accessing a key of it.

You are converting the whole array into an ObjectID instead you want to convert individual values. Use .map() with ObjectId constructor

removing list from `t.nonNull.list.field("deleteUser"{/***/}) fixes the problem.

You are trying to do two things in one middleware. And that's not a good idea. Because when you need to check if the user is authenticated elsewhere, you need to copy and paste your code in this place. This is a bad pattern. Instead of that you should create separate middleware or guard(check nestjs doc about guards). And this guard will check if user is authenticated or not. If it is then guard let request further. In other case guard throw Http exception 401 Unauthorized. As for file uploading you could use multer. About file uploading check corresponding section of nestjs doc(how to upload file nestjs doc).