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

Handling contact addresses #43

Closed
rayankans opened this issue Aug 10, 2021 · 1 comment · Fixed by #45
Closed

Handling contact addresses #43

rayankans opened this issue Aug 10, 2021 · 1 comment · Fixed by #45

Comments

@rayankans
Copy link
Collaborator

The ContactAddress interface used to rely on the PaymentAddress interface which has since been dropped. This raises a few questions:

  • Is this the right spec to define addresses?
  • Should the current interface be changed to have closer HTML/autocomplete alignment?
@marcoscaceres
Copy link
Member

  • Is this the right spec to define addresses?

It's as good an any.

  • Should the current interface be changed to have closer HTML/autocomplete alignment?

That might be good, but it really depends on how much implementer appetite there is for renaming/refactoring things.

I think we should maybe just provide a non-normative mapping in the spec for now... if we start seeing people complain, we can look at renaming things.

rayankans added a commit that referenced this issue Aug 12, 2021
This seems uncontroversial so there's no need to include it in the spec.
rayankans added a commit that referenced this issue Aug 12, 2021
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

Successfully merging a pull request may close this issue.

2 participants