Default View Namespace Imports

[Corey Kaylor]

Just thinking out loud. Any reason that we shouldn't by default import the namespaces for any input models and view models the application is aware of into CommonViewNamespaces? This would eliminate ever having to add using statements to your template files. Any drawbacks?

[Jeremy D. Miller]

The only possible thing I can think of is performance, but at first blush I really like this suggestion.

Naming collisions maybe?

On Mar 27, 2013, at 11:44 AM, Corey Kaylor <co...@kaylors.net> wrote:

Just thinking out loud. Any reason that we shouldn't by default import the namespaces for any input models and view models the application is aware of into CommonViewNamespaces? This would eliminate ever having to add using statements to your template files. Any drawbacks?

--
You received this message because you are subscribed to the Google Groups "FubuMVC Development Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fubumvc-deve...@googlegroups.com.
To post to this group, send email to fubumv...@googlegroups.com.
Visit this group at http://groups.google.com/group/fubumvc-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Corey Kaylor]

Yeah, fully qualifying at that point would fix the problem.

[Corey Kaylor]

Could definitely make it settings driven. .AutoImportModelNamespaces();

[Jeremy D. Miller]

I think I like the idea of making it be "opt out."  Make things easy by default.

[Matt S.]

Wow. Yeah, that would be nice.

[RobertTheGrey]

I like it!