Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

Attribute Routing: Implement Name #734

Closed
rynowak opened this issue Jul 1, 2014 · 1 comment
Closed

Attribute Routing: Implement Name #734

rynowak opened this issue Jul 1, 2014 · 1 comment
Assignees
Milestone

Comments

@rynowak
Copy link
Member

rynowak commented Jul 1, 2014

This should be done once link generation is available

@javiercn
Copy link
Member

2 days + PR time

@javiercn javiercn reopened this Jul 28, 2014
@danroth27 danroth27 modified the milestones: 6.0.0-alpha3, 6.0.0-alpha4 Aug 12, 2014
javiercn added a commit that referenced this issue Aug 26, 2014
1. Added support for Name in attribute routing. Name can be defined using [RouteAttribute]
and the different Http*Attributes, for example [HttpGet].

2. Names defined on actions always override names defined on the controller.

3. Actions with a non empty template don't inherit the name from the controller. The name
   is only inherited from the controller when the action template is null or empty.

4. Multiple attribute routes with different templates and the same name are not allowed.
javiercn added a commit that referenced this issue Aug 29, 2014
1. Added support for Name in attribute routing. Name can be defined using [RouteAttribute]
and the different Http*Attributes, for example [HttpGet].

2. Names defined on actions always override names defined on the controller.

3. Actions with a non empty template don't inherit the name from the controller. The name
   is only inherited from the controller when the action template is null or empty.

4. Multiple attribute routes with different templates and the same name are not allowed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants