Skip to content

Conversation

@abhinavk96
Copy link
Contributor

@abhinavk96 abhinavk96 commented Aug 12, 2019

Fixes #3020
Fixes #3382
Fixes #2077
Fixes #2366
Fixes #2972

Copy link
Member

@kushthedude kushthedude left a comment

Choose a reason for hiding this comment

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

#2077 Still exists @CosmicCoder96

@kushthedude
Copy link
Member

Also #2366

@fossasia fossasia deleted a comment Aug 14, 2019
@fossasia fossasia deleted a comment Aug 16, 2019
@fossasia fossasia deleted a comment Aug 16, 2019
@abhinavk96 abhinavk96 changed the title fix: resolve whack-a-mole behavior of time/date pickers fix: resolve whack-a-mole behavior of time/date pickers & add validations to date-time Aug 16, 2019
@fossasia fossasia deleted a comment Aug 16, 2019
// break;
// case 'end':
// defaultOptions.startCalendar = this.$().closest('.fields').find('.ui.calendar.time.picker');
// break;
Copy link
Member

Choose a reason for hiding this comment

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

@CosmicCoder96 Remove the comments, Else tested every widget works well 🎉

Copy link
Contributor Author

@abhinavk96 abhinavk96 Aug 16, 2019

Choose a reason for hiding this comment

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

leaving these comments.. because someday we might want the time validation to change it's values according to its start counterpart, removed it for now because jquery ui calendar does not compare date while matching time fields, which sort of broke the UI.

uds5501
uds5501 previously approved these changes Aug 16, 2019
Copy link
Contributor

@uds5501 uds5501 left a comment

Choose a reason for hiding this comment

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

Tested components :

  • Wizard step 1 (start and end dates)
  • ticket sales dates
  • session-speaker forms

They are working fine. Marking LGTM

@fossasia fossasia deleted a comment Aug 16, 2019
Copy link
Member

@shreyanshdwivedi shreyanshdwivedi left a comment

Choose a reason for hiding this comment

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

  • Date/Time picker while in wizard1 and session wizard working fine
  • Date/Time in ticket is working fine
  • There is a glitch in discount code date/time picker. Whenever I choose time, the date is set to invalid and vice versa (for start date-time)
    Screenshot_2019-08-17 Create Discount codes Tickets orderAPI Events Open Event

@kushthedude
Copy link
Member

  • time

Not reproducible on my local, Any specific steps?

@shreyanshdwivedi
Copy link
Member

@kushthedude just edit the time and date while creating the discount code. You'll see it
@uds5501 can you reproduce it?

@abhinavk96
Copy link
Contributor Author

@shreyanshdwivedi @kushthedude The behavior shreyansh noted might be for some discount codes who previously had a null value. I can't recreate it while creating new ones or existing valid ones. Though I did was able to recreate that when I forced a false value for the start time inside DB.

@abhinavk96
Copy link
Contributor Author

abhinavk96 commented Aug 16, 2019

@shreyanshdwivedi

just edit the time and date while creating the discount code.

you mean edit using backspace?

@shreyanshdwivedi
Copy link
Member

shreyanshdwivedi commented Aug 16, 2019

@CosmicCoder96 there was a weird behavior. When I followed links to create discount code and edited it, I was able to reproduce it.
But once I refreshed the URL directly, I couldn't. I'm still getting error when I create it using Create Dicount Code button and then editing the start date to a greater value than end date and then updating start time

@abhinavk96
Copy link
Contributor Author

@shreyanshdwivedi Caught the source, thanks for the review 👍 fixed now.

});
let currentDiscountCode = model.discountCode;
let event = this.modelFor('events.view');
currentDiscountCode.set('validFrom', moment().toISOString());
Copy link
Contributor Author

@abhinavk96 abhinavk96 Aug 16, 2019

Choose a reason for hiding this comment

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

this was the problem 😈 converting it to string made it invalid to moment js computations.
@shreyanshdwivedi @kushthedude

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

4 participants