You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a need to define various options for our date pickers, and want to be able to apply these options on the element without having to manually edit each one. I know of the global provider for setting options, but this sets it globally for all datepickers within the application. Is there a way to set up options and then pass that into the element, so that all of the elements that need those options can get it from one source?
In this example, we have 6 date pickers. the first four get their options from the options object, while the last two are plain vanilla datepickers with no customization.
I'm aware we could have a global configuration and the tweak at the element level, but that seem too overreaching. I'm also aware that we could have all the options set on each element, but that's too limited (we want first four to always remain the same and use the same options, don't want chance of dsync). I feel there should be a middle layer between global / local customization where you can give it the options. Is this possible in the current implementation?
The text was updated successfully, but these errors were encountered:
blitzmann
changed the title
Is there a way to pass in on options object?
Is there a way to pass in an options object?
Nov 16, 2018
Hi there!
We have a need to define various options for our date pickers, and want to be able to apply these options on the element without having to manually edit each one. I know of the global provider for setting options, but this sets it globally for all datepickers within the application. Is there a way to set up options and then pass that into the element, so that all of the elements that need those options can get it from one source?
eg:
In this example, we have 6 date pickers. the first four get their options from the options object, while the last two are plain vanilla datepickers with no customization.
I'm aware we could have a global configuration and the tweak at the element level, but that seem too overreaching. I'm also aware that we could have all the options set on each element, but that's too limited (we want first four to always remain the same and use the same options, don't want chance of dsync). I feel there should be a middle layer between global / local customization where you can give it the options. Is this possible in the current implementation?
The text was updated successfully, but these errors were encountered: