Skip to content

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

Merged
merged 46 commits into from
Sep 15, 2020
Merged

feat: make publishing event clearer #5011

merged 46 commits into from
Sep 15, 2020

Conversation

maze-runnar
Copy link
Contributor

@maze-runnar maze-runnar commented Sep 8, 2020

Fixes #4673

from #4942

Checklist

  • I have read the Contribution & Best practices Guide.
  • My branch is up-to-date with the Upstream development branch.
  • The acceptance, integration, unit tests and linter pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@vercel
Copy link

vercel bot commented Sep 8, 2020

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/eventyay/open-event-frontend/2q1p1a2bh
✅ Preview: https://open-event-frontend-git-fork-maze-runnar-clearer.eventyay.vercel.app

@maze-runnar
Copy link
Contributor Author

@iamareebjamal please review

@codecov
Copy link

codecov bot commented Sep 8, 2020

Codecov Report

Merging #5011 into development will increase coverage by 0.16%.
The diff coverage is 14.70%.

Impacted file tree graph

@@               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              
Impacted Files Coverage Δ
app/components/forms/wizard/attendee-step.js 0.00% <ø> (ø)
app/components/forms/wizard/basic-details-step.js 18.98% <ø> (-2.54%) ⬇️
app/components/forms/wizard/other-details-step.js 0.00% <ø> (ø)
.../components/forms/wizard/sessions-speakers-step.js 0.00% <ø> (ø)
app/components/forms/wizard/sponsors-step.js 0.00% <ø> (ø)
app/controllers/events/view.js 0.00% <ø> (ø)
app/mixins/event-wizard.js 1.05% <0.00%> (ø)
app/components/events/view/publish-bar.ts 17.24% <17.24%> (ø)
app/utils/computed-helpers.js 21.27% <0.00%> (-0.47%) ⬇️
... and 4 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3275795...d130537. Read the comment docs.

Copy link
Member

@mariobehling mariobehling left a 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
    1. 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
    1. A name
    2. A location or online event link
    3. 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

@mariobehling
Copy link
Member

mariobehling commented Sep 8, 2020

Screenshot from 2020-09-08 12-47-34

Please also

  • increase the spacing between the the first row of buttons and the second row "View/Publish" button.
  • add a horizontal line of 100% page width above the second row

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.

@maze-runnar
Copy link
Contributor Author

maze-runnar commented Sep 8, 2020

Button Spacing, open preview in new window, adding horizontal line, Showing the text "This event is published. Any changes you make will appear on your live event." and "This event is currently not published. It is in draft mode and it is not visible publicly.".
Screenshot from 2020-09-08 21-10-35
Screenshot from 2020-09-08 20-49-28
Screenshot from 2020-09-08 20-39-27
Screenshot from 2020-09-08 19-51-26

@maze-runnar
Copy link
Contributor Author

maze-runnar commented Sep 8, 2020

Publish and unpublish popup are not working the same as in the dashboard section. So made all other changes.

@mariobehling
Copy link
Member

Thank you, please also change

  • Rename "Forward" to -> "Next"
  • Live events are missing the "Save" feature (Clicking "Save" should save the current wizard step and exit to the dashboard of this event)

Screenshot from 2020-09-08 18-40-42

@mariobehling
Copy link
Member

When creating a new event, it is not clear yet how to publish it.

Screenshot from 2020-09-08 18-56-04

I think it should only be possible to publish an event once the event draft has been saved.

Therefore please display:

  • A "Publish" button that is in grey color as long as the event has not been saved as a draft.
  • A horizontal line as in other views
  • In this initial step - before the event has been saved, please also show the following text above the horizontal line: "You can preview the event after you have saved it as a draft. You can publish the event after filling in the required fields."

@maze-runnar
Copy link
Contributor Author

  • Live events are missing the "Save" feature (Clicking "Save" should save the current wizard step and exit to the dashboard of this event)

I am not getting it, why live events should option to save,while it can be published.

@maze-runnar
Copy link
Contributor Author

I think it should only be possible to publish an event once the event draft has been saved.

Therefore please display:
A "Publish" button that is in grey color as long as the event has not been saved as a draft.

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?

@maze-runnar
Copy link
Contributor Author

changing msg when event is not saved for first time, and forward -> Next
Screenshot from 2020-09-08 23-54-45
Screenshot from 2020-09-08 23-37-28

@maze-runnar
Copy link
Contributor Author

make publish button grey when event is not saved for first time -
Screenshot from 2020-09-09 00-09-47

@maze-runnar
Copy link
Contributor Author

maze-runnar commented Sep 8, 2020

Made all the required changes, not sure that save button should display when event is published.

@mariobehling
Copy link
Member

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.

@mariobehling
Copy link
Member

mariobehling commented Sep 8, 2020

Still missing:

  • Show "Save" button after event is published
  • Publish (opens a pop up - same as "Publish" on the dashboard / afterwards exits to event dashboard).
    • Show the pop up
  • Unpublish (opens a pop up - same as "Unpublish" on the dashboard / afterwards exits to event dashboard)
    • Show the pop up

Screenshot from 2020-09-08 20-53-28

@maze-runnar
Copy link
Contributor Author

maze-runnar commented Sep 15, 2020

now it's working correctly
captured (1)

@@ -46,6 +47,10 @@ export default Mixin.create(MutableArray, CustomFormMixin, {
];
},

ticketsPresent: computed('data.event.tickets.@each', function() {
Copy link
Member

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

Copy link
Member

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

@@ -227,6 +232,44 @@ export default Mixin.create(MutableArray, CustomFormMixin, {
callback(true);
});
},

openConfirmModal() {
Copy link
Member

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

this.set('isPublishUnpublishModalOpen', true);
},

togglePublishState() {
Copy link
Member

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

@iamareebjamal
Copy link
Member

You have added some functions back which are not needed. Please remove them

addItem(type, model) {
if (type === 'socialLinks') {
this.get(`data.event.${type}`).pushObject(this.store.createRecord(model, {
identifier: v1()
}));
} else if (type === 'customLink') {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove this?

@iamareebjamal
Copy link
Member

iamareebjamal commented Sep 15, 2020

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

@iamareebjamal
Copy link
Member

Now ticketsPresent is back again. Please review the changes locally before committing and then before pushing

@maze-runnar
Copy link
Contributor Author

Um, now you removed a random if statement which was necessary. There always seems to be either some random think added or removed.

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.

@iamareebjamal
Copy link
Member

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

Copy link
Member

Codacy Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ app/controllers/events/view.js  -4
         

See the complete overview on Codacy

@maze-runnar
Copy link
Contributor Author

I think it's ok now.

@iamareebjamal iamareebjamal changed the title fix: making publishing event clearer fix: make publishing event clearer Sep 15, 2020
@iamareebjamal iamareebjamal changed the title fix: make publishing event clearer feat: make publishing event clearer Sep 15, 2020
@auto-label auto-label bot added feature and removed fix labels Sep 15, 2020
@iamareebjamal iamareebjamal merged commit e28bfe6 into fossasia:development Sep 15, 2020
@mariobehling
Copy link
Member

Glad, it is working now! Thank you.

@maze-runnar maze-runnar deleted the clearer branch December 13, 2020 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wizard: Make Event Saving, Draft Mode, Publishing Clearer
4 participants