feat: Allow Name Generator to disable attach to DevTools #14425
Merged
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.
What does the pull request do?
Add property
AvaloniaNameGeneratorAttachDevTools
to Name Generaator that allow it to disable attach to DevToolsWhat is the current behavior?
Name Generaator
if the target isWindow
, the DEBUG constant is defined and the project referencesAvalonia.Diagnostics
, always generate code for Attach to DevTools. This behavior does not allow you to easily customize DevTools options. To do this you need to modify each window constructor to invokeInitializeComponent(attachDevTools: false);
instead ofInitializeComponent();
.What is the updated/expected behavior with this PR?
When add following to .csproj does not generate code to Attach to DevTools
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues