Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why cal:View.Context is object and not string? #892

Open
a44281071 opened this issue Nov 14, 2023 · 0 comments
Open

Why cal:View.Context is object and not string? #892

a44281071 opened this issue Nov 14, 2023 · 0 comments

Comments

@a44281071
Copy link

a44281071 commented Nov 14, 2023

MyNamespace.Views.StudentViewModel.
locate to:
MyNamespace.Views.StudentView.
locate with context (Details):
MyNamespace.Views.Student.Details.

It just work with a string 'Details', so why use object type?

A question that was raised a long time ago: It pollutes the name definition.
I must def a namespace like 'xxx.Student.xxx'. But I also have a model named 'xxx.Student.cs'. It's weird to reference members. 'Student' is a class, and also is namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant