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
Fix event date view #643
Fix event date view #643
Conversation
@nileshgulia1 Can you please do a couple of changes? We cannot ship it just like this: We need to make it a bit more human. Plone does this, which is not also super fancy, but it is something... We need to use momentjs (we already have it in Volto) to make it look nicer. Please can you take a look at it? Also, I want you to add a proper EventView for the Event content type (add it to the default config), Line 18 in 70dcec1
|
@nileshgulia1 I know that there is no mockup for it, but can you please also make it show all the fields that are in the Event content type? Like location, etc... Take a look into the Plone template to know which ones are shown (the ones in the main tab, except the metadata (change etc..) ) |
@nileshgulia1 do you plan to continue to work on this? |
@tisto Yes, already done some research on it, currently busy here. I will
continue it maybe next week.
…On Tue, Mar 19, 2019, 18:25 Timo Stollenwerk ***@***.***> wrote:
@nileshgulia1 <https://github.com/nileshgulia1> do you plan to continue
to work on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#643 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AVP6xZhWEKJG5HliKAC4M_PzUqFdoacuks5vYN5ZgaJpZM4bJqgB>
.
|
Continued work on this during Beethoven Sprint. Up to now, we have a view that shows all fields except recurrence. Also, i18n and some tests are needed. |
Added more tests. Will have a look at recurrence in the next few hours, at least for the View. |
@pnicolli what's the status of this PR? Still WIP or something we should review/look into? |
@tisto Unfortunately I don't remember the precise state of the PR but I think it was still waiting for recurrence handling. The conf took most of my energy in the last weeks, we are releasing the final version of the site (the one with the schedule!) in the next few days, I would have some time to work on other things after that, but it's completely ok if @nileshgulia1 goes on from where I left off, I have other PRs I can work on :) Nilesh, if you find anything that I wrote that you want to discuss, feel free to contact me or comment the code directly here. |
@pnicolli Hi. Thanks for quick fixes. I'm looking forward to add more conditionals for event occurring biweekly, 'on specific days' and 'repeating events' etc. |
@pnicolli I think the basic functionality for recurrence is implemented now. Can you please do a quick sweep review and let me know of any changes? |
@nileshgulia1 I'm testing the recurrence. I'll let you know asap, but I have a first suggestion. I see you have recently reinstalled react-helmet, but that was recently removed because unmaintained (see https://docs.voltocms.com/upgrade-guide/#forked-helmet-into-volto-core). I think you just need to change one import statement and you can remove that again.
I noticed you implemented the parsing of the rrule string yourself. Have you considered using a js library for that? For example this one: https://github.com/jakubroztocil/rrule
What do you think @sneridagh ?
@pnicolli yeah better stick to known libraries that already focus in the problem and solves it. |
@nileshgulia1 @pnicolli The recurrence widget for the form is not included in this PR, right? So we still have to wait for it to setup recurrence, is that correct? Any plans/updates for it?
Also, the EventWhen.jsx
has two components, I'm ok with that if both are super related, but the name can be improved a bit maybe. What do you think?
@sneridagh Exactly, the widget is not part of this PR, this one just shows the recurrence info coming from Plone. @giuliaghisini is developing the widget in a separate branch. Would you prefer to have a Draft PR about that in order to see the state of the development? Regarding this PR: Yeah, the reason why I kept them together is that they are related and are based on the same date formatting function. I will commit new names in a few minutes. |
@pnicoli It’s fine! No draft PR required at all! Thanks for the info! |
#632
-cc @sneridagh