-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat: make publishing event clearer #5011
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
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/eventyay/open-event-frontend/2q1p1a2bh |
@iamareebjamal please review |
Codecov Report
@@ Coverage Diff @@
## development #5011 +/- ##
===============================================
+ Coverage 22.68% 22.85% +0.16%
===============================================
Files 488 489 +1
Lines 5183 5159 -24
Branches 21 28 +7
===============================================
+ Hits 1176 1179 +3
+ Misses 4003 3976 -27
Partials 4 4
Continue to review full report at Codecov.
|
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.
Please read the issue description again carefully and rename the buttons accordingly. There is no point to review your PRs if you dont read the issues.
1. When event is created and still unpublished (Draft Mode)
- Requirement for saving a draft is only
- to have an event name
- show buttons:
- Discard (only when event was never saved - when creating the event: It does not save the event and discards any data that was entered. After that direct user back to dashboard of all events. If user has saved an event previously, there is no "Discard" possible anymore, then show "Cancel" and send user back to specific event dashboard.)
- Cancel (cancels changes of the wizard step and exists to event dashboard)
- Previous (except for first step)
- Next (saves changes and goes to the next step, except for last step)
- Save draft (saves draft and exits wizard to this event's dashboard)
- below the above option show another section with two buttons
- Show a horizontal line with 100% width of the page
- Show the text "This event is currently not published. It is in draft mode and it is not visible publicly."
- Preview (open in new tab)
- Publish (opens a pop up - same as "Publish" on the dashboard / afterwards exits to event dashboard). Please show this button as "gray" as long as the event does not have the minimum date listed necessary for publishing an event.
2. After an event is published already (Live Event)
- Requirement for an event to be publishable is, that it has
- A name
- A location or online event link
- A ticket
- below the above savings/next/previous options show another section with two buttons
- Show the text "This event is published. Any changes you make will appear on your live event."
- View (open in new tab)
- Unpublish (opens a pop up - same as "Unpublish" on the dashboard / afterwards exits to event dashboard)
3. Top menu "Wizard Steps"
When a user clicks a top wizard menu item the following action should take place:
- Cancel changes of the current tab and load the menu tab
Please also
As you can see in the screenshot the buttons show "Preview/Unpublish". Expected is "View/Unpublish". The View button does not open in a new tab as described in the issue. Sorry, but this seems a bit unfair - do you expect other devs to review your PRs and point out each of the list items on the issue to you one by one? Please go through each point first by yourself and do help us to shorten the review time that is required by paying more attention to each point. Thank you. |
Publish and unpublish popup are not working the same as in the dashboard section. So made all other changes. |
When creating a new event, it is not clear yet how to publish it. I think it should only be possible to publish an event once the event draft has been saved. Therefore please display:
|
I am not getting it, why live events should option to save,while it can be published. |
previously it was mentioned in issue like toicket, location and name is required for publishing an event. After these changes user can't publish events in first time? |
Made all the required changes, not sure that save button should display when event is published. |
Yes, please display a "Save" button when the event is published as well. |
app/mixins/event-wizard.js
Outdated
@@ -46,6 +47,10 @@ export default Mixin.create(MutableArray, CustomFormMixin, { | |||
]; | |||
}, | |||
|
|||
ticketsPresent: computed('data.event.tickets.@each', function() { |
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 bring this back? It's not needed
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.
Now this is back again
app/mixins/event-wizard.js
Outdated
@@ -227,6 +232,44 @@ export default Mixin.create(MutableArray, CustomFormMixin, { | |||
callback(true); | |||
}); | |||
}, | |||
|
|||
openConfirmModal() { |
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 bring this back? It's not needed
app/mixins/event-wizard.js
Outdated
this.set('isPublishUnpublishModalOpen', true); | ||
}, | ||
|
||
togglePublishState() { |
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 bring this back? It's not needed
You have added some functions back which are not needed. Please remove them |
app/mixins/event-wizard.js
Outdated
addItem(type, model) { | ||
if (type === 'socialLinks') { | ||
this.get(`data.event.${type}`).pushObject(this.store.createRecord(model, { | ||
identifier: v1() | ||
})); | ||
} else if (type === 'customLink') { |
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 remove this?
Um, now you removed a random if statement which was necessary. There always seems to be either some random thing added or removed. Please carefully review the changes yourself before committing. There are way more review cycles than needed. You need to improve the self-evaluation phase of your PRs |
Now |
yeah, I don't know why this happens to me a lot, and in this PR more than a lot. I am trying to improve it. |
Before pushing. Go through the code where you made the changes and check all the things previously mentioned are removed or not, and nothing else is removed. If you're trying to do it using GitHub UI, then it definitely won't be correct because it is extremely easy to make mistakes there and not realize what you are removing and what extra thing you removed. Nor is there any way to review the final changes before pushing |
Complexity decreasing per file
==============================
+ app/controllers/events/view.js -4
See the complete overview on Codacy |
I think it's ok now. |
Glad, it is working now! Thank you. |
Fixes #4673
from #4942
Checklist
development
branch.