-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(datetime): Add component #1240
Conversation
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 realize this is work in progress. Couple typos that might trip you up:
return <ElementType {...rest} className={classes}>{children}</ElementType> | ||
} | ||
|
||
DropdownMenu._meta = { |
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.
CalendarMonth._meta
type: META.TYPES.MODULE, | ||
} | ||
|
||
DropdownMenu.propTypes = { |
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.
CalendarMonth.propTypes
Thanks for the note, I'll take a look at this branch later tonight and resolve the issue. |
Codecov Report
@@ Coverage Diff @@
## master #1240 +/- ##
===========================================
- Coverage 99.73% 19.07% -80.66%
===========================================
Files 151 159 +8
Lines 2624 2862 +238
===========================================
- Hits 2617 546 -2071
- Misses 7 2316 +2309
Continue to review full report at Codecov.
|
Fixed: -static PropTypes
+static propTypes I also pushed a lot of cleanup so I could browse the code a little easier. |
Looks like we'll need to reabse this branch to master to get the commits in order. All the typings were moved from This is 1:1 with how the JS files are setup as well. LMK if you run into any issues with the rebase cleanup and I'll help out. |
No worries. I rebase periodically anyway so this will be just one more link in the chain. Didn't do much over the last few days because of life but i'm back at it this week. |
4d54f2f
to
87d50ed
Compare
I've pushed some cleanup and a rebase to the latest master. I think we should start breaking this PR down into small shipments and releasing it. This will allow us to focus on one chunk at a time and do a good job on just that. As we polish and release each piece, we can bring it back into this branch and prepare the next release. Do you think we could somehow release Date only as the first component, the Time, and Datetime? I'm wondering if it makes sense to break these down that way API wise as it does release wise. Let me know your thoughts. |
Heads up, I'll be pushing some more refactors and cleanups for a bit here. |
OK, after pushing the latest I think we can ship Datetime with basic support first, then perhaps follow-up with the range support. DateTimeGridI pushed a generic DateTimeGrid that is used in all but the Month view. It allows an easier construct the table cells, just pass a single array of as many cells as you want and tell the DateTimeGrid how many columns to fit them into. It will chunk out the Rows for you. This will also give us the ability to handle different layouts, since the DateTimeGrid just takes a single array of cell props objects. We can use this array to build any layout. We can even, later on, expose a TODOI'd like to factor out the DayCell into the DateTimeGrid but am not 100% sure on how yet. I'd also like to move the dateUtils to the Datetime directory and perhaps remove more, if possible (I removed some already). That's all I got for now, thanks for all the work on this and the patience dealing with my limited availability. We're getting close to something here 👍 |
Whats the status of this issue? |
I'm also interested in this feature and can dedicate some time this week to test/code/document/brainstorm or whatever is needed. |
It's coming together, late stage development. There are a few things that
require feedback - in particular the momentjs branch which decouples date
handling to support both native js dates as well as moment/moment-timezone
dates (or any other time framework).
…On Mon, Apr 24, 2017 at 10:19 AM, Gregory Potdevin ***@***.*** > wrote:
I'm also interested in this feature and can dedicate some time this week
to test/code/document/brainstorm or whatever is needed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1240 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA8Lena3iGagJIwWgDbL6GfmgN1rX2FXks5rzGkzgaJpZM4LwH1O>
.
|
b1fec82
to
575dc34
Compare
Hi guys, how is it going :) |
d39be38
to
2bb587a
Compare
d8a6977
to
641e968
Compare
1be8dd8
to
ebf33a6
Compare
Can't wait, any progress ? Do you need help testing it? |
Let me know if there is anyway I can help push this forward. |
Waiting eagerly for this to be completed. This is a very frequently used component in forms. Available for helping push this out soon. |
Same here, count me in if you need anything |
If anyone would like to hop in here's some more info. Conformance tests are passing and there are plenty of doc site examples. What's needed is to run the doc site, try the examples, and fix the bugs. Bug fixes should also have tests written for them. As soon as all the doc site examples are working with passing tests, this can be shipped. 🎉 |
How is it going guys ? Any news on this ? |
Patiently waiting. Anything I can do to speed this up? |
This is the final piece missing for all my forms using SUI. Can't wait! |
All I want for Christmas is SUI datepicker 🎄 🎁 📆 😆 |
Hey everyone! I think we are all excited to ship this. At the same time, there is only so much bandwidth that main contributors to this project have to give to open source work. The nice thing is that it's open source and we are happy to accept pull requests from anyone that moves this project/feature forward. Per @levithomason's comment above, as soon as doc site examples are working and tests are passing for the reported bugs, this can be shipped. @Gallevy you asked if there is anything you can do to move this forward... we welcome any time you can dedicate to fixing any of the remaining bugs. Anyone else who has commented wanting to know what is going on, you are also welcome to help out. <3 |
@brianespinosa When will we be able to use this? :) |
Could this PR be merged so that testing it is made easier? Thank you |
If you'd like to contribute to the development of this feature, please email me[at]levithomason.com. This thread produces too much noise and distracts from the focus. |
A few collaborators have emailed me and pushed this work forward. You are amazing ❤️. I've ported this branch to our repo for easier management. I'm merging any well authored PRs against this effort. See #2821 for the Datetime branch on the main repo |
This is a work in progress mainly focused on exploring the possiblity of adding a datetime component which supports date ranges, time and localisation.
TODO
Bugs and Features
<< < Mo, Yr > >>
. double chevrons change year, single change month, mo(e, { value })
wherevalue
is the proposed new value.Docs
Week starts Sunday
example toFirst Day Of Week
show two examples, start on Sun, another on Monday.Cleanup
/addons
TODO
s in/Datetime
onDateSelect
args to match other callbacks, withevent
first.