-
Notifications
You must be signed in to change notification settings - Fork 132
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
display calendar legend #12403
Comments
@egorwow70 what you refer to ui5 is the calendar components, not the datepicker. We have the same for datepicker - https://fundamental-ngx.netlify.app/#/core/calendar |
Let me bring this with the designers first. |
@egorwow70 we have the feature for special days, we just need to display them in the calendar (respectively in datepicker and datetimepicker) |
@alexhristov14 Can you check whether we need to implement this in styles first and then bring it in ngx? |
Is this a bug, enhancement, or feature request?
bug
Describe your proposal.
Hello, fundamental-ngx team. We are implementing the app using angular and fundamental-ngx/core and have a requirement to display a date picker with special dates and legend displayed. As I can see, special dates can be displayed with current library functionality, but the legend is missing. Is it possible to fix it on the library side?
Legend should be supported by both fd-calendar and fd-date-picker from fundamental-ngx/core
As for the technical side, I think it will be easy for devs, who are using the lib, to configure that via those objects (SpecialDayRule), for example via new field - title or label or legendLabel (naming up to you):
I am not a designer, but this is an example what we need:
Sapui5 example - https://sapui5.hana.ondemand.com/#/entity/sap.ui.unified.Calendar/sample/sap.ui.unified.sample.CalendarSpecialDaysLegend
Can you handle that on the application side
No.
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
Did you check the documentation and the API?
Yes.
Did you search for similar issues?
Yes
The text was updated successfully, but these errors were encountered: