Andrzej Bakun

@ElderJames so what would be preferred solution here? If the choice was mine, I'd choose `SuffixIcon` as it is immediately clear what it is about. Also, should `Select` include also...

So...the more I look at this the more I think we should drop "Icon" part. Mostly because in both cases these are `RenderFragment` type of attributes. This allows user to...

When applying this change, also `SuffixIcon` in `DatePicker`/`RangePicker` should be taken into account.

I believe the first day issue was discussed in PR #1054. But this was never addressed again I think. We could probably discuss this again and see if it is...

The codesandbox.io was not working for me, but I think [this](https://brianmin.tech/react-edit-text/) also presents the idea.

## Performance best pracitces - when dealing with `[Parameters]`: - whenever possible use primitive types ([source](https://docs.microsoft.com/en-us/aspnet/core/blazor/webassembly-performance-best-practices?view=aspnetcore-5.0#avoid-unnecessary-rendering-of-component-subtrees)) - if primitive types are not possible, configure `ShouldRender` to return `false` for components...

Nice find! Still haven't dug into source generators (in my todo list). Maybe this will push me, but this really looks interesting.

I think #1120 is a connected issue.

~Just noticed one more - when no date is selected yet, the picker already shows current date as selected: ~ ~It should look like this: ~ ~This issue applies to...

Quoted from [this PR #1431](https://github.com/ant-design-blazor/ant-design-blazor/pull/1452#issuecomment-833405696) > By the way, I found a problem, but this problem exists in the current version(0.8.0). > RangePicker(date mode with timer) cannot select the correct...