All right, so welcome back again. So in this session again, we'll be trying to see an analysis that comes to do with our CLR. So in this session, we try to see how to allow abbreviations and then not to allow abbreviation. So by default, if we go with the same symposia lecture, which is basically a lie. Does that help? Right is going to work perfectly, right?

So that means that even if I do something like this, it's still going to work. Right? I just gave it only three, not the full hope it's still able to identify that particular weight. If I give the full stuff is able to work. If I give just a default, it's still going to work, right? So why is it able to do that, because by default, it's allowing us to use all forms of abbreviation, which is very, very useful to enable the user to be able to use any format of the argument supplied.

So let's try another example. So we have first name here, right? So I guess I want to actually work on it without printing everything and just go back to this. Then go it does just name it, I'll specify the name that I want to use. But if I give this a name like, say, David, it's going to activate right? Your name is David and your name is not.

Now in case I do want to bring the first image I just come with just faced like this. So I go it first is to go to identify that faced representative first name. So can you give us the same result. So your name is David, that is the basic idea behind this particular option. So they by default, at pass allows us to be able to use abbreviations right, so these are all forms of permissions. So, I can do the same thing like fare and this goes to go to work.

And if I go with a short format to this F, is still going to work. Right. So that is one one interesting thing about it very, very interesting. Very cool. So in case you want to restrict this particular feature to make it more strict threaded pessimists enter the full name, then just come back to your parser parser here, didn't just add a particular officer, let's add it here is going to be allow a brief then you set that one to false, right? So if I set to false, now it's no more going to work, it's going to give us an error, right when you do that.

So allow a brief is set to false. So if I come back to the same thing that we're doing, and I run it again, this is going to add goes by default is going to accept it to F segment is not recognized it is may be recognized and that's very interesting, right? Very cool. It is not sometimes it is totally strict and give it F and before it awake. So this fn is referring to our short format here, which is this pivot. Now let's go back and do the same thing or not.

This time we are using the long format of fist and then it's going to work is going to give us an arrow that basically allows a recognized argument first, right. So once you set the allow a brief to force that feature is disabled today. user has to actually type the entire stuff by going with first name, or rely on the short format of the event right there if that is the only way it's going to work, otherwise no go into it. So that's the basic idea behind allow applications. But it's recommended to actually set that alarm to truth, because by default is already set to true. If I set it to true, I can come back again, there aren't any of them.

It's going to work perfectly relative to the idea behind it switches recommended to allow this one to be true, right. So that's it helps a user as to okay so except you want it to be more strict, and it's going to use the allow a brief set to false to thank you for watching, and see in the next session. Stay blessed.