| "explorer.fileNesting.enabled": true, | |
| "explorer.fileNesting.expand": false, | |
| "explorer.fileNesting.patterns": { | |
| "pubspec.yaml": ".flutter-plugins, .packages, .dart_tool, .flutter-plugins-dependencies, .metadata, .packages, pubspec.lock, build.yaml, analysis_options.yaml, all_lint_rules.yaml", | |
| ".gitignore": ".gitattributes, .gitmodules, .gitmessage, .mailmap, .git-blame*", | |
| "readme.*": "authors, backers.md, changelog*, citation*, code_of_conduct.md, codeowners, contributing.md, contributors, copying, credits, governance.md, history.md, license*, maintainers, readme*, security.md, sponsors.md", | |
| "*.dart": "$(capture).g.dart, $(capture).freezed.dart", | |
| }, |
| using System.Threading.Tasks; | |
| using Newtonsoft.Json; | |
| using Refit; | |
| using System.Net.Http; | |
| using System; | |
| namespace wms_xamarin | |
| { | |
| public class LoginApi | |
| { |
One of the best ways to investigate a problematic Xamarin.Android Binding is to first ensure you have the proper tooling available: