-
-
Notifications
You must be signed in to change notification settings - Fork 771
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
Change Bounty Details #1968
Change Bounty Details #1968
Conversation
@@ -0,0 +1,72 @@ | |||
|
|||
// Overwrite from shared.js | |||
function trigger_form_hooks() { |
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.
Unexpected empty function 'trigger_form_hooks'. (no-empty-function)
|
||
// Overwrite from shared.js | ||
function trigger_form_hooks() { | ||
}; |
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.
Unnecessary semicolon. (no-extra-semi)
app/dashboard/views.py
Outdated
"""Change bounty.""" | ||
|
||
|
||
if request.body: |
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.
E303 too many blank lines (2)
Codecov Report
@@ Coverage Diff @@
## master #1968 +/- ##
==========================================
- Coverage 28.11% 27.91% -0.21%
==========================================
Files 136 136
Lines 11025 11130 +105
Branches 1475 1499 +24
==========================================
+ Hits 3100 3107 +7
- Misses 7816 7913 +97
- Partials 109 110 +1
Continue to review full report at Codecov.
|
Any feedback on this one? 😄 |
it still says WIP in the PR title and theres a few TODOs in the diff. is this ready for review? |
Yes, it's WIP because of the comments in the PR. I asked for first review in the linked issue ;) |
QA notes
happ y to QA more when the items in the definition of done on the spec are completed |
@@ -754,6 +754,8 @@ var do_actions = function(result) { | |||
const show_suspend_auto_approval = document.isStaff && result['permission_type'] == 'approval'; | |||
const show_admin_methods = document.isStaff; | |||
const show_moderator_methods = document.isModerator; | |||
const show_change_bounty = isBountyOwner(result); |
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.
or is_admin
</head> | ||
|
||
<body class="interior submit_bounty" style="background-color: #FFFFFF;"> | ||
{% include 'shared/tag_manager_2.html' %} |
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.
why build a whole new form. why not just re-use the new_bounty
form?
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 take a look at the new changes and modify the template if necessary for easier reuse. 👍
app/dashboard/views.py
Outdated
timezone.datetime.fromtimestamp(deadline), | ||
timezone=UTC) | ||
|
||
item = params.get('attached_job_description', '') |
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 wonder if we could use django forms for any of this repetitive code.... cc @mbeacom
|
||
<h1>{% trans "Bounty Details Changed" %}</h1> | ||
<br> | ||
|
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.
should we list out the details that have changed.. ?
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 don' think that would be needed! cause the funder would see it on the bounty page upon redirection
@@ -0,0 +1,3 @@ | |||
Bounty Details Changed | |||
|
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.
no data in this email
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 included the bounty.txt template 😕
Thanks for review 👍
That's odd, seems to be a conflict with new changes on master since I worked on it.
Yep, I transfer the bounty details with this method.
That I wasn't sure about. Will be removed.
The same problem like 1. |
app/dashboard/views.py
Outdated
keys = ['experience_level', 'project_length', 'bounty_type', 'permission_type', 'project_type'] | ||
|
||
if request.body: | ||
can_change = (bounty.status in Bounty.OPEN_STATUSES) or (bounty.can_submit_after_expiration_date and bounty.status is 'expired') |
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.
E501 line too long (136 > 120 characters)
Ready for review (again) 👍 . |
just tested... seems to work well 👍 |
@pinkiebell quick rebase and then we merge ? |
bounty details ('experience_level', 'project_length', 'bounty_type', 'permission_type', 'project_type') can be changed if the bounty is still on 'the happy path' by the funder or staff. Fixes #1928
@thelostone-mc Done! 👍 |
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.
tested it out ! LGTM
@PixelantDesign this is how it looks @pinkiebell Oh i just noticed should we update the placeholder text ? |
@thelostone-mc |
@pinkiebell the button on the bounty details page |
And fix one status code.
@thelostone-mc Done 👍 |
sweet!! will merge this in once @PixelantDesign reviews it 👍 |
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.
Looking good @pinkiebell!
On the buttons, could we change....
- 'Change Bounty Details' ----> 'Edit Issue Details'
- Change Details Screen...could we change the commit button to "Update Issue Details"
Nice work!
My other question is, if a funder is updating the issue details..should the following also happen...
Thoughts from the group? @owocki @vs77bb @thelostone-mc @pinkiebell. |
@PixelantDesign |
LGTM!
I think we should hold off on this for now. There's already enough comments on the Github thread, IMO. If it turns out to be an issue, we could include 'Approval' vs. 'Permissions' bounties in a v2 of the PR @oogetyboogety is working on regarding the Gitcoin Bot copy updates! |
sounds good. Let's merge @thelostone-mc @SaptakS ? |
@pinkiebell thanks for the contribution ^_^ |
Sweeeeeeeeeetttt! |
bounty details ('experience_level', 'project_length', 'bounty_type',
'permission_type', 'project_type')
can be changed if the bounty is still on 'the happy path' by the funder
or staff.
Fixes #1928