-
Notifications
You must be signed in to change notification settings - Fork 52
[WC-2892]: Calendar improvements #1628
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
base: main
Are you sure you want to change the base?
Conversation
729563e
to
092f468
Compare
packages/pluggableWidgets/calendar-web/src/utils/calendar-utils.ts
Outdated
Show resolved
Hide resolved
3c4cc51
to
cf6e6bc
Compare
83c13d2
to
e45f6cd
Compare
901cdef
to
f39a11a
Compare
… adjust time building logic
This reverts commit af8d6d8.
f39a11a
to
fc2c48c
Compare
<description>The hour at which the day view starts (0–23)</description> | ||
</property> | ||
<property key="maxHour" type="integer" defaultValue="24"> | ||
<caption>Day end hour</caption> | ||
<description>The hour at which the day view ends (1–24)</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.
That is a bit confusing. What (0-23) and (1-24) mean?
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.
We can probably check if starting hour is less than ending hour in editorConfig. And give an error otherwise.
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.
These are for start and end hours of the day. Can start 0-23 earliest and end 1-24 latest.
<enumerationValue key="day">Day</enumerationValue> | ||
<enumerationValue key="week">Week</enumerationValue> | ||
<enumerationValue key="month">Month</enumerationValue> | ||
<enumerationValue key="work_week">Custom</enumerationValue> |
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.
It should probably say "Custom work-week" or even "Work week".
<property key="showSunday" type="boolean" defaultValue="false"> | ||
<caption>Sunday</caption> | ||
<description>Show Sunday in the custom work-week view</description> | ||
</property> | ||
<property key="showSaturday" type="boolean" defaultValue="false"> | ||
<caption>Saturday</caption> | ||
<description>Show Saturday in the custom work-week view</description> | ||
</property> |
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 guess Saturday should go before Sunday as this probably determines order in the UI.
</property> | ||
</propertyGroup> | ||
<propertyGroup caption="Visible days"> | ||
<property key="showMonday" type="boolean" defaultValue="true"> |
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.
If those propertties are related to customView only, suffix their name with customView
as well as you did with customViewCaption
. So customViewShowMonday
, etc. Any other related properties can benefit from this approach as well.
Pull request type
New feature (non-breaking change which adds functionality)
Description
Added: