Fix #10364 - Adding now option and minute sensibility in Datetime fields #10368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In this PR, the option "now" is added to the default value list in the datetime field editing in the Studio module. Additionally, the internal value of the "today" item has been modified, as it was already using the value "now".
Furthermore, the variable
datetime_combo_minute_interval
is created to indicate the interval of minutes that will be displayed in datetime fields, in case the default value of every 15 minutes is not desired.Additionally, the sensitivity of the minute hand of datetime fields whose default value is "now" is modified. The sensitivity is set to 1 so that the minutes are always displayed correctly.
Motivation and Context
This change is required to enhance the functionality of the datetime fields in the Studio module. It adds flexibility by allowing the option "now" and enables customization of the minute interval displayed in datetime fields.
How To Test This
Types of changes
Final checklist