-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QNTM-5869: Search keywords split mechanism #9271
Changes from all commits
592d004
8957593
f31c89c
ad954ff
872ae52
6ea8014
35a8d60
3d78511
e40a85b
302889c
9d0719a
815e694
7405eb9
1b2ae4a
8aacc9e
ce19e59
83a11a9
bba5180
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -291,6 +291,19 @@ public bool EnableTSpline | |
} | ||
} | ||
|
||
/// <summary> | ||
/// Indicates whether experimental search mode is turned on. | ||
/// For internal debug use only. Do not use! | ||
/// </summary> | ||
public bool ExperimentalSearch | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should have a summary /// tag if this a public API - does it need to be public? |
||
{ | ||
get { return model.SearchModel.ExperimentalSearch; } | ||
set | ||
{ | ||
model.SearchModel.ExperimentalSearch = value; | ||
} | ||
} | ||
|
||
/// <summary> | ||
/// Indicates whether search results should be truncated (currently to 20 items). | ||
/// </summary> | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -785,10 +785,15 @@ | |
Header="{x:Static p:Resources.DynamoViewDebugMenuShowDebugAST}" | ||
IsChecked="{Binding ShowDebugASTs}"></MenuItem> | ||
<MenuItem Focusable="False" | ||
Name="ExperimentalSearch" | ||
Name="TruncateSearchResults" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @ColinDayOrg FYI I renamed your menu item name There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch, thanks. I am assuming that the "TruncateSearchResults" menu has been checked to test if it still works as expected after this change? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I just did a quick test to verify that the menu still works in the current master codebase after this specific change, so it seems ok to me. |
||
IsCheckable="True" | ||
IsChecked="{Binding TruncateSearchResults}" | ||
Header="{x:Static p:Resources.DynamoViewDebugMenuTruncateSearchResults}" /> | ||
<MenuItem Focusable="False" | ||
Name="ExperimentalSearch" | ||
IsCheckable="True" | ||
IsChecked="{Binding ExperimentalSearch}" | ||
Header="{x:Static p:Resources.DynamoViewDebugMenuExperimentalSearch}" /> | ||
<MenuItem Focusable="False" | ||
Name="ForceReexec" | ||
Header="{x:Static p:Resources.DynamoViewDebugMenuForceReExecute}" | ||
|
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.
Just as a question; should this code be wrapped in #if DEBUG statements? Probably not necessary, but I am doing the same type of code and wanted to get the group thought about if it is needed/wanted or not.
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.
I think because this code is already in the debug only menu it's fine not to use a compiler flag. On the other hand, for performance impacting code - like
Console.WriteLine
I would use a debug flag:https://stackoverflow.com/questions/18464833/console-writeline-effect-on-performance