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

API Explorer: Link Generation #885

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

API Explorer: Link Generation #885

rynowak opened this issue Jul 28, 2014 · 1 comment
Assignees
@javiercn
Labels
3 - Done enhancement needs design
Milestone
1.0.0-beta1

Comments

@rynowak
Copy link
Member

rynowak commented Jul 28, 2014

Depends on #883

Design and implement support for generating partially-expanded link templates given an action. Consider exposing in RFC-6570 format.

Needs to be broken down further once we have design.
@rynowak rynowak self-assigned this Jul 28, 2014
@yishaigalatzer
Copy link
Contributor

This item depends on a decision on action selection.

@danroth27 danroth27 assigned javiercn and unassigned rynowak Sep 23, 2014
@danroth27 danroth27 modified the milestones: 6.0.0-beta1, 6.0.0-alpha4 Sep 23, 2014
javiercn added a commit that referenced this issue Oct 8, 2014
@javiercn
[Fixes #885] API Explorer: Link Generation
b5a4ba6 
1) Expose the simplified relative path template by cleaning up constraints, optional and catch all tokens from the template.
2) Expose the parameters on the route template as API parameters.
3) Combine parameters from the route and the action descriptor when the parameter doesn't come from the body. #886 will refine this.
4) Expose optionality and constraints for path parameters. Open question: Should we explicitly expose IsCatchAll?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@javiercn javiercn

Labels
3 - Done enhancement needs design
Projects
None yet
Milestone
1.0.0-beta1
Development

No branches or pull requests
4 participants
@yishaigalatzer @rynowak @danroth27 @javiercn