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

Default values #52

Open
plinss opened this issue Jan 24, 2020 · 5 comments
Open

Default values #52

plinss opened this issue Jan 24, 2020 · 5 comments

Comments

@plinss
Copy link

plinss commented Jan 24, 2020

I noticed the implementation allows specifying default values in the template, which is cool, but is not supported by the RFC.

Maybe this feature should be added to the RFC?

@sigmavirus24
Copy link
Collaborator

Can you share what you mean by "specifying default values"? I can't figure out what you're talking about. I only wrote things according to the specification.

@plinss
Copy link
Author

plinss commented Jan 25, 2020

Sure, you can have a template: “{foo=bar}” and if the caller does not provide a value for ‘foo’, the result is “bar”. Maybe I’m missing something but I don’t find that in the RFC.

@sigmavirus24
Copy link
Collaborator

Huh, now I'm wondering why I implemented that nearly 7 years ago.

@plinss
Copy link
Author

plinss commented Jan 25, 2020

Looks like it was in an earlier draft: https://tools.ietf.org/html/draft-gregorio-uritemplate-02#section-3.2 and removed in version 06.

Don't get me wrong, I'm not proposing you remove the feature, I'd rather see a new version of the RFC that brings this feature back. I'm just pointing it out to raise the disconnect.

@sigmavirus24
Copy link
Collaborator

Well I don't have control over that and have little enthusiasm to interact with the IETF WG over this.

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

2 participants