feat: Hide the DatePicker button when readOnly is true

[skvale]

Description

A readOnly DatePicker field should not have a button

Breaking Change: A readOnly DatePicker field does not have an InputGroup Button

IE11

[netlify]

Deploy preview for fundamental-react ready!

Built with commit fd4af75

https://deploy-preview-1234--fundamental-react.netlify.app

[jbadan]

I hate to make this change more complicated, but do we need to do this in fundamental styles too?

Edit: there is no readOnly example in fundamental-styles, so we're safe to proceed here.

[bcullman]

I hate to make this change more complicated, but do we need to do this in fundamental styles too?

Edit: there is no readOnly example in fundamental-styles, so we're safe to proceed here.

I came here to ask about this too:

I see it is not documented there, but what is the Fiori3 stance on what readonly fields should look like?

[jbadan]

@bcullman It's not defined anywhere in the spec - DatePicker documentation mostly centers around the Calendar in the popover with very little about the actual input field.

[skvale]

Are we OK merging this and picking that up as a conversation in a Thursday meeting?

[bcullman]

@bcullman It's not defined anywhere in the spec - DatePicker documentation mostly centers around the Calendar in the popover with very little about the actual input field.

if it's not documented, why do we think the solution is to hide the add-ons? I get that this is A possible solution, but I am not certain it is the right one. We need someone from UX to weigh in/followup on this

[skvale]

We talked with Brandon and he thought it made sense to go with this change as it currently is.