-
Notifications
You must be signed in to change notification settings - Fork 19
Widgets work with both ~users and Teams #112
Conversation
Nice! I've made a Anyone up for reviewing this? If not I'll get to it when I can ... |
Should I worry about these checks failing? |
@mattbk Yes. It looks like our linter ain't happy with your formatting. ;-) |
Okay, I see it now. lib/v1/api.js |
I think tests are based on the old |
Looking at these files in order?
|
I think it's failing on this part of
|
That works. Hot. |
/me waiting for Travis to run green ... |
This makes test results easier to read.
Hold your horses, I have to understand how tests work first. |
!m @mattbk |
It looks like only giving can be anonymous now, not receiving. That doesn't help my brain work better, though. |
This reverts commit 066ba6c.
I ended up merging |
I'm satisfied with the final product; it's a heck of a mess of commits, though. 🐺 @whit537, @techtonik, any comments? |
Github now allows squash and merge commits! 💃 |
|
||
// If username exists, it's a ~user, not a team. Build URL accordingly. | ||
if (data.username) { | ||
link('profile-link', gratipayURI + encodeURIComponent(data.username) + '/'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we want to insert a ~
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure how those rewrites end up working. I know that if I don't put a ~ in, it still works. If it is better to include the ~, then we can do that.
As I read it, this PR tries to treat the
I'm not sure that's the right approach to take, both because it introduces tech debt into our widget code ("receiving" in this PR no longer means "receiving," it means "receiving or taking"), and because it's not as true to our new data model as it could be. I think a better approach will be to let I propose that we whittle this PR down to just the test changes that make sense to keep, and pick up with additional changes in new PRs. |
I can work on that, unless someone else wants to jump in. |
I might need clarification. You mean make this PR about ~users and build a new PR for teams? |
Got it. Now I get to learn how to clone my PR without losing things. |
Based on discussion at #112 (comment). Breaking up that PR into more manageable chunks.
…into team-experiments
Based on discussion at #112 (comment). Breaking up that PR into more manageable chunks.
Shuttering this pull request because it changes v1 widgets, which is not the plan at #103 (comment). Keeping the branch in place until I grab what I want for a real v2. |
I took a crack at aligning the default widget code with the new public.json output from Gratipay.com. Comments are welcome; I'm sure there are ways to break what I've done.