-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Move Avalonia.NameGenerator to the main repository #10407
Conversation
* Add XAML parser based on XamlX
* NameDirectiveTransformer.cs * Build-time diagnostics
* Add basic MiniCompiler unit tests * Add XamlX tests stub file
* Fix attached properties resolution * Strip out controls that aren't IControl * Be more strict and check the namespace * Update packages, throw when class is not partial * Use internal access modifier explicitly * Move the attribute to Avalonia.Controls namespace * Further documentation updates * Add the badges
* Strip out the namespace * Strip out the instantiation * Actually strip out the transformer
* Refactoring, decomposition, more unit tests * Support x:FieldModifier * Use Xamarin.Forms API for x:FieldModifier * Use <RestoreSources /> directive, bump Avalonia * CRLF dance * Use Fluent theme * Move Avalonia packages to Directory.Build.props * Bump test SDK version
…ces attribute (#22) * feature: Generate x:Name mapping without the GenerateTypedNameReferences attribute. * fix: Update README.md
…Failure (#23) * Update README.md * Don't crash when something goes wrong * Add back the warning * Update version.json
* Switch over to using x:Class * The MsBuild property is no longer required * Documentation updates * Bring back the AXN0003 warning * Bring back AXN0002 * Mocks for unit tests * Actually use the mock in unit tests * Bump version
You can test this PR using the following package version. |
@worldbeater @robloo done. Restore sandbox and reorganized code. |
You can test this PR using the following package version. |
You can test this PR using the following package version. |
This generator (I assume it's in analyzer folder) is not generating InitializeComponent() method. What should we config for this? |
I also encounter this issue. Is there any switch we need to enable in the .csproj file? |
In the telegram chat was found a workaround: |
For the proper solution, nuget props should include Avalonia.Generators.props which is missing currently |
What does the pull request do?
To be done, but out of scope of this PR:
How was the solution implemented (if it's not obvious)?