Add new boolean operators #465
Conversation
|
Learn Build status updates of commit 8ebe1bc: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit e6f496f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit e00dfcf: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 57280a6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit b472541: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit f316b4b: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@microsoft-github-policy-service agree company="Esri" |
|
Learn Build status updates of commit 6d4c826: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@jfversluis @TheCodeTraveler do you know who may be able to review this documentation PR? |
|
I'll sort this 👍 |
There was a problem hiding this comment.
@stephenquan thank you for this update. I have just added one comment, please let me know what you think
|
Learn Build status updates of commit 4b85c05: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 3d79428: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Document the new boolean operators that are being introduced in CommunityToolkit/Maui#2181
Here are the new operators / constants being documented:
?:&&||(alternates:andor)==!=>=><=<(alternates:gegtlelt)!trueorfalseDocument differences these operators look between C# and XAML (because of XAML escaping).
By XAML escaping I mean that
&&in XAML looks like&&and>=in XAML looks like>=.To make it developers to use these operators in either C# and XAML, alternate English-only operators were also given.
Also, because the XAML escaping didn't render correctly, it was necessary to put code escpaing on all operators. i.e. even the existing operators needed to be escaped. This caused most of the file to be updated even though only a handful of new operators were introduced.