{"action":"opened","issue":{"url":"https://api.github.com/repos/reactiveui/ReactiveUI/issues/1679","repository_url":"https://api.github.com/repos/reactiveui/ReactiveUI","labels_url":"https://api.github.com/repos/reactiveui/ReactiveUI/issues/1679/labels{/name}","comments_url":"https://api.github.com/repos/reactiveui/ReactiveUI/issues/1679/comments","events_url":"https://api.github.com/repos/reactiveui/ReactiveUI/issues/1679/events","html_url":"https://github.com/reactiveui/ReactiveUI/issues/1679","id":337318771,"node_id":"MDU6SXNzdWUzMzczMTg3NzE=","number":1679,"title":"WireUpControls for Android.Support.V4.App.Fragment is missing ResolveStrategy parameter","user":{"login":"NZSmartie","id":1032029,"node_id":"MDQ6VXNlcjEwMzIwMjk=","avatar_url":"https://avatars1.githubusercontent.com/u/1032029?v=4","gravatar_id":"","url":"https://api.github.com/users/NZSmartie","html_url":"https://github.com/NZSmartie","followers_url":"https://api.github.com/users/NZSmartie/followers","following_url":"https://api.github.com/users/NZSmartie/following{/other_user}","gists_url":"https://api.github.com/users/NZSmartie/gists{/gist_id}","starred_url":"https://api.github.com/users/NZSmartie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NZSmartie/subscriptions","organizations_url":"https://api.github.com/users/NZSmartie/orgs","repos_url":"https://api.github.com/users/NZSmartie/repos","events_url":"https://api.github.com/users/NZSmartie/events{/privacy}","received_events_url":"https://api.github.com/users/NZSmartie/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-01T20:16:50Z","updated_at":"2018-07-01T20:16:50Z","closed_at":null,"author_association":"NONE","body":"**Do you want to request a *feature* or report a *bug*?**\r\n\r\nBug\r\n\r\n**What is the current behavior?**\r\n\r\nWhen using `[WireUpResource(\"some_id_ name\")]` on properties inside a `Android.Support.V4.App.Fragment` fragment, then calling `this.WireUpControls();` in `OnCreateView`, an exception is thrown much like #1231\r\n\r\n**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem**\r\n\r\n1. Create a new Fragment that is based on `Android.Support.V4.App.Fragment` \r\n1. Add a Control property to be wired up:\r\n\r\n   ```C#\r\n        [WireUpResource(\"text_some_name\")]\r\n        public TextInputEditText SomeTextInput { get; private set; }\r\n   ``` \r\n1. Inflate with a layout with ids that do not match the property name in the fragmet's class but instead match with the `WireUpResource` attribute.\r\n1. Override `OnCreateView(...)` with:\r\n\r\n   ```C#\r\n        public override View OnCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState)\r\n        {\r\n            var view = inflater.Inflate(Resource.Layout.some_fragment_dialog, container, false);\r\n\r\n            if (view != null)\r\n                this.WireUpControls(view);\r\n\r\n            return view;\r\n        }\r\n   ```\r\n1. Note that `this.WireUpControls(view);` does not have any overrides that accept a `ResolveStrategy ` parameter.\r\n\r\n**What is the expected behavior?**\r\n\r\nSupplying `ResolveStrategy.ExplicitOptIn` would allow use of properties with `WireUpResource` attributes\r\n\r\n**What is the motivation / use case for changing the behavior?**\r\n\r\nTo be more consistent with `WireUpControls` method that is used with an `Activity` or `Fragment` class \r\n\r\n> Note that I'm using using the Fragment class from the Android support library instead of the default Fragment (as recommended by the Official Android Documentation)\r\n\r\n**Which versions of ReactiveUI, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the [latest stable](https://www.nuget.org/profiles/reactiveui) and [development snapshot](https://reactiveui.net/docs/getting-started/installation/nuget-packages/development-package-feed)**\r\n\r\nv8.3.1 (stable)\r\n\r\nI've yet to test this against development\r\n\r\n**Other information (e.g. stacktraces, related issues, suggestions how to fix)**\r\n\r\nSuggest adding another `WireUpControls` extentionmethod in `ReactiveUI.AndroidSupport/ControlFetcherMixin.cs` that accepts the same (or similar) parameters much like `WireUpControls` for an `Activity` or `Fragment` (As seen in `ReactiveUI/Platforms/android/ControlFetcherMixins.cs`)"}}
{"actor":{"display_login":"NZSmartie"}}