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 not use webfinger.js? #7

Open
silverbucket opened this issue Mar 13, 2015 · 3 comments
Open

why not use webfinger.js? #7

silverbucket opened this issue Mar 13, 2015 · 3 comments

Comments

@silverbucket
Copy link

I think it's a good idea to re-use as many existing, single purpose, libraries as possible. Like you are discussing in the remotestorage.js issues at the moment. So why don't we use https://github.com/silverbucket/webfinger.js here?

@michielbdejong
Copy link
Owner

Yeah, I originally wanted to reuse all existing rs.js code, but didn't manage to untangle it.

But yeah, I could replace these 7 lines with webfinger.js, let me try that.

@silverbucket
Copy link
Author

It would replace more than just those 7, but yeah - I think it's a good idea to use a bunch of small single purpose libraries which focus on their problem domain, hopefully with tests etc. so we can offload as much technical debt as possible. once you get together a build process and a package.json, you can pin the version to follow the 2.x branch, I'm following semver so the API wont break for 2.x

@michielbdejong
Copy link
Owner

OK, so I did this (took me exactly 30 minutes, looking at the comment dates :) ): #8

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