Skip to content
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

Add .UseReactiveUI() call to xplat template #88

Merged
merged 1 commit into from
Nov 14, 2022

Conversation

schnerring
Copy link
Contributor

I was studying the templates and found that xplat is missing the .UseReactiveUI() call.

Related:

@schnerring
Copy link
Contributor Author

My change shouldn't break the iOS build, however I don't have an environment where I can test this.

@Takoooooo
Copy link
Contributor

PR makes sense. Will check later why does IOS fails

@maxkatz6
Copy link
Member

I don't think ReactiveUI is compatible with iOS of current SDK. It definitely wasn't couple of months ago.

@Gillibald
Copy link

I vote against this change because it introduces a dependency that isn't really required

@maxkatz6
Copy link
Member

In this case PackageReference should be removed as well. It's just unused now.

@schnerring
Copy link
Contributor Author

In this case PackageReference should be removed as well. It's just unused now.

It's not unused. The reference to ReactiveUI could be removed, but it would still be referenced implicitly through the AvaloniaTest project reference. AvaloniaTest uses the Avalonia.ReactiveUI package.

@schnerring
Copy link
Contributor Author

schnerring commented Apr 29, 2022

My understanding from comparing the templates is that the project generated from the app-mvvm template and the AvaloniaTest project from the xplat template are functionally the same - both MVVM ReactiveUI projects. Except that platform-specific code was separated from AvaloniaTest into other projects.

My change just consolidates one of the small differences between these projects.

@maxkatz6
Copy link
Member

Build should work with latest reactiveui (18.0.7+) reactiveui/ReactiveUI#3184

@schnerring
Copy link
Contributor Author

schnerring commented Apr 30, 2022

Cool!

Do we wait until you bump the version in:

https://github.com/AvaloniaUI/Avalonia/blob/master/build/ReactiveUI.props#L3

I could also push a commit referencing 18.0.7+ explicitly.

@maxkatz6 maxkatz6 closed this May 3, 2022
@maxkatz6 maxkatz6 reopened this May 3, 2022
@Takoooooo
Copy link
Contributor

Takoooooo commented May 4, 2022

Try merging master to the branch now,i assume it was an issue on our side and i will later think about whether it is a good idea to merge this.

@maxkatz6
Copy link
Member

maxkatz6 commented May 6, 2022

Btw, this call was added only to Desktop call. But not to other projects.
I.e. it should be something like this in AppDelegate for iOS:

protected override AppBuilder CustomizeAppBuilder(AppBuilder builder)
{
    return base
        .CustomizeAppBuilder(builder)
        .UseReactiveUI();   
}

It's not unused. The reference to ReactiveUI could be removed, but it would still be referenced implicitly through the AvaloniaTest project reference

It's unused in actual xplat template. Makes sense to add, but main repo should update reactiveUI to 18.x before that.

Copy link
Member

@maxkatz6 maxkatz6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging as we didn't have time to remove ReactiveUI from the default xplat template.

@maxkatz6 maxkatz6 merged commit c15e0cc into AvaloniaUI:master Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants