-
Notifications
You must be signed in to change notification settings - Fork 106
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
Inability to Edit Weekly Cron for Every Day of the Week in react-js-cron #62
Comments
Hi, If I understood your use case, it's normal.
It's the same thing. This cron component is designed to make you read the most easy format.
Let me know if I understood what you meant? |
Hi @xrutayisire, thank you for your quick response. Yes, you've understood the issue correctly. However, when we set the defaultPeriod to "Weekly" and then set the cron value as "10 10 * * *" [using default value for cron], it should persist the period as "Weekly." But it appears to be changing the period in the dropdown to "Daily." Could you please look into this? Your assistance is greatly appreciated. |
Hi, It's true that the default value for period should be persisted. It's necessary to rework the period management and the fallback system. If not, I will do it, but I'm not really sure when. Could be something in November. Thank you for the bug report 🙏 |
Thanks @xrutayisire for response. I am also little bit busy with work. But I will try to look into this. Meanwhile if you get the time then kindly fix it. Thanks in advance. |
Hi @xrutayisire , |
Hi, No sorry I really have no time since quite some time now. I'm not sure when I could take care of that in a near future. 😕 |
Description:
I am utilizing the react-js-cron to create weekly cron expressions. However, when attempting to edit a cron expression for all days of the week, the editor automatically switches to a daily mode. Specifically, when I input a weekly cron expression for every day of the week, such as '10 10 * * *,' the editor incorrectly converts it to a daily cron format.
Here are the steps to reproduce the issue, broken down point by point:
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: