Correct approach for extending e.g. the DatePicker module

[ghost]

Hi all,

I hope someone can help me. I am currently involved in evaluating clarity.design for use in an Angular app. However, an absolute necessity for us is the possibility of being able to (simply) modify some aspects of the behavior and html structure of certain components.

For example: in the ClrCalendar component (ClrDatepicker module), we would need to add weeknumbers and a "today" button. However, being relatively new also in Angular I am currently struggling a bit so to say. One approach I was trying was to exploit @Directives, but these do not allow me to change a components templates.

However, is my goal achievable in a sane way?

[hippee-lee]

For the Today button is this not doing what you need it to do?

I'm not quite sure what is meant by weeknumbers can you elaborate?

I do not think it is possible or a good idea to modify templates at runtime. However, could the app wrap what it needs inside a component you control in a way that adds the additional UI / info?

[ghost]

Thank you for your answer!

The "current month" button is indeed similar, but not exactly what I am after: what I would like to implement is a button that sets the datepicker value to todays date – immediately closing the overlay.

As for the weeknumbers, I have attached a screenshot:

You are absolutely right regarding "not a good idea to modify templates at runtime".
However, what I tried was:

• Define a component that "overwrites" the tag used by the ClrCalendar class ("clr-calendar", I think it was) and adjusting the template in the process; however, I guess Angular does not allow to do such things (which is plausible);
• I managed to define a directive for the main tag ("clr-date-container"), however, there seems no good way of refine some aspects of the template;
• Finally, as a last resort, I tried to extend ClrDateContainer – however, I soon ran into issues with private services.

The thing is, we are a bit between a rock and a hard place. :) Unfortunately we need to frequently modify components – but we do not have the resources to write our own. In the same time, I would like to keep all changes easily traceable and manageable, making it easy for all colleagues to work with an already fine library!