Should namespaces start with Assets. ?

I am using ReSharper which has a pretty awesome feature to auto arrange my namespaces with just a few clicks. The thing is that every time it does that, let's say we have a script in Scripts/MyMonoBehaviour.cs, and now ReSharper says that the corresponding namespace to this file is Assets.Scripts, while I consider it to be simply Scripts.

Which is the correct namespace?

1) Scripts
2) Assets.Scripts

If 1) is the correct one, then how can I tell ReSharper to exclude the Assets from the potential namespace refactoring?

 

There is no "correct" namespace. Namespaces are purely for organization of scripts, and thus can, and should be, named in a way so you can easily keep your scripts organized. The default behavior in Visual Studio for namespace naming is to use "Assembly > (sub)folder names". This "default namespace" can be changed however using the following steps:

Code (csharp):

1. -> Project
2. -> Properties
3. -> Default Namespace

Having said that, personally I just use what gets generated by default, which is Assets.Scripts.Whatever.Structure.I.Use and I can imagine most do.

 

@Timelog thank you for the quick response! I'm sorry for the inaccurate word that I used, a better one would be "the most common one" instead of correct, sorry again about that. Anyway for my last few projects I've been using ReSharper's default suggestion as well which is Assets.etc.

For example (idk if you are using GPG Plugin for Unity) which namesaces omit the Assets. part should I let ReSharper adjust all the namespaces in their classes there to fit the Asset. pattern? Here I'm talking just what would be a good practice.

Thanks! )))

 

I found another way to omit the Assets folder though.

Cheers and thanks again! )))

 

No, because imo you then step into a very dangerous rabbit hole. While adjusting namespaces should not harm the package in any way, there are most likely more patterns and practices used in that package that ReSharper doesn't like, some of which will break the package if auto changed making you have to fix them manually costing you a lot of time. I would just keep the package as is, and use your patterns and practices only in your code.

 

Going one step further, think about maintaining the assets in the future. Each time the publisher pushes an update you'll have to go through this process again.

 

Thank you guys ))) Really appreciate your time spent on helping me out here ))