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

HTML/CSS Touch ups on Bounty Details Page #399

Closed
jasonrhaas opened this issue Feb 12, 2018 · 6 comments
Closed

HTML/CSS Touch ups on Bounty Details Page #399

jasonrhaas opened this issue Feb 12, 2018 · 6 comments
Assignees

Comments

@jasonrhaas
Copy link
Contributor

Tweak the details page a bit so that the columns and headers line up nicely and its easier to read.

@owocki
Copy link
Contributor

owocki commented Feb 12, 2018

might be able to fold this in with #323

@jasonrhaas
Copy link
Contributor Author

@owocki ah yes I think I can probably merge those changes in with the new stuff for multiple fulfillments if you are happy with the design. Looks like an improvement.

@owocki
Copy link
Contributor

owocki commented Feb 13, 2018

i... dont love the design on that issue but maybe im marred by staring at the old one too much. maybe @PixelantDesign will have more developed thoughts than i do :P

@jasonrhaas
Copy link
Contributor Author

jasonrhaas commented Feb 13, 2018

ok well lets keep the new design discussion in that PR, this issue is just to fix some fulfillment acceptance things. That one seems like more of a slight re-design. Will get this taken care of and close out this issue.

@owocki
Copy link
Contributor

owocki commented Feb 13, 2018

ok cool

@jasonrhaas
Copy link
Contributor Author

jasonrhaas commented Feb 14, 2018

ok so this one is complete with the exception that we need to fix a bug that is occurring on the bounty fulfillment. Currently the API/Database is not updating the bountyfulfillment table properly which a fulfillment gets accepted. I have some code in there that displays which fulfillment was accepted, but it won't work unless the database is updated. Opening a new Issue for this bug.

Reference #428

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