This repository was archived by the owner on Jul 9, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 374
refactor: remove tildes #3266
Merged
Merged
refactor: remove tildes #3266
Changes from all commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
2aa6fa0
remove tildes
beyackle 34adef5
Merge branch 'master' into beyackle/tildes
beyackle c541a49
add no-bitwise rule
beyackle adb5729
Merge branch 'master' into beyackle/tildes
beyackle 8e5e20a
Merge branch 'master' into beyackle/tildes
beyackle d10d089
Merge branch 'master' into beyackle/tildes
beyackle f03a9a2
update luPublisher with typo fixes and some cleanup
beyackle 63bbd09
fix typo
beyackle f87eaa3
Merge branch 'master' into beyackle/tildes
beyackle 5fd41d8
Merge branch 'master' into beyackle/tildes
beyackle 75d35ae
remove tildes
beyackle e896efc
add no-bitwise rule
beyackle f49e848
update luPublisher with typo fixes and some cleanup
beyackle 84b2cf5
fix typo
beyackle b886f73
Merge branch 'beyackle/tildes' of https://github.com/microsoft/BotFra…
beyackle 6a7cb51
Merge branch 'master' into beyackle/tildes
beyackle 36fd810
Merge branch 'master' into beyackle/tildes
beyackle e78207e
Merge branch 'master' into beyackle/tildes
beyackle 21d3614
Merge branch 'master' into beyackle/tildes
beyackle 498dc86
Merge branch 'master' into beyackle/tildes
beyackle 1c47348
Merge branch 'master' into beyackle/tildes
beyackle f5bcb27
Merge branch 'master' into beyackle/tildes
beyackle a3a33eb
Merge branch 'master' into beyackle/tildes
beyackle b3d4c38
fix endpoint issue
beyackle File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cant this just be types[ExpressionType.integer] instead of doing includes everytime?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at this again, I'm not sure we can do anything about it yet. Types is an array but ExpressionType.integer is a string; we want to check if the string is a value in the array, so
includesis appropriate here. The more correct thing here would be to make types aSet<string>, but that ought to be its own cleanup ticket later - it's a non-trivial amount of work.