fix(popover): use correct enum name and type for showon param #2168
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- The correct enum is https://docs.telerik.com/blazor-ui/api/telerik.blazor.components.popovershowon - it is a nullable parameter with no default value, as this way it caters for the case where programmatic approach only is desired. The default value here is misleading - this was never the case in the component and is an issue only in the documentation
radkostanev
added
the
merge-to-production
|
Hello @radkostanev, Check the below option if you would like to automatically generate PR to production. The automation uses the branch for the cherry-pick, and then will delete the branch. Please, do not delete it manually.
|
yanisslav
approved these changes
Jun 18, 2024
ikoevska
approved these changes
Jun 18, 2024
|
Here you are the link to your PR to production: 2171 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default value here is misleading - this was never the case in the component and is an issue only in the documentation