All language subtitles for 7. Namespaced

In the previous lecture, I have introduced your modules.

They have created a reference to module we are calling exchange.

And in these actually continue, I will show you what issues we can have in the future and the way how

we can, how we can prevent them or how we can fix them.

All right, let's begin in Ah.

Yeah, let's stay here in our homeland view, and the issue we can have is way the dispatching of this

action and get exchanges.

Imagine if people have multiple modules and maybe we don't have an exact figure exchanges, but let's

say we will have a good data or get something.

OK, so get data.

Let's say you'll have a dispatch.

But this is a very generic name, and maybe we will have a get data on multiple modules.

Maybe good data will be not only in the exchange module.

So imagine you have I get data here, but you'll have multiple modules like, let's say we will have

here.

You will be used as modules, then we will have opportunities, opportunities module.

And so on, and some of these modules, you can have a functionality that will interfere with the other

functionality, that naming will be exactly the same.

So in this case, if you would call a here dispatch, get data.

You would call not a boat functions, but you would call the first module that is defined, so imagine

you would have here more modules here.

You will have you will have you here.

Module opportunities.

Opportunity is even learning about opportunities later, what I mean by that opportunities.

And you will have your users.

All right, users, and to exchange and board of opportunity will define a good date as it will have

a good data.

Did data here, and you would have a good data here.

OK, so in this case, to do this better than good data, what I mean, to pick from which module I

want to call get a good data.

I want to quote from here or from here.

OK.

Currently, I cannot specify in 100 of you, I can just call this project data.

I can't specify what I mean by getting a data.

I would like to call this one or at this one.

So I can see you would have these conflicts.

How you can prevent these conflicts is very simple.

You can do this.

You can go to your exchange module.

And in the the father can specify one property called names based names based like this and you will

market us through.

Well, Martin, his name spaced any time you would like, you want to execute functionality to dispatch

some action.

You need to prefix your action with the name of the module and you know, exactly in which module is

this action that resides?

It's not going to have a namespace through we can go to home dot, we'll.

And of this bed, we can call now, prefix of the module is an exchange slash.

And now the name of the action.

And this is get exchanges.

So now, now, now I know exactly from which module I would like to get the specialist action or I would

like to get these parties action to.

OK, that prefix of the module, I know by going to the store index suggests the prefix.

And get exchanges is the action.

All right, let's try it out, let's save it and go back to browser refresh, and after one second,

you will see your data.

So everything is working, everything is in order here.

All right, very quick lecture.

Let's continue in the next lecture.