when I was playing with the v2/account endpoint I wrote a micro library to just pull minute details from it
using Newtonsoft.Json;
namespace DangerBot.GW2.V2.Account.Objects
{
/// <summary>This class describes a player account.</summary>
public class Account
{
/// <summary>Gets or sets the accounts id.</summary>
[JsonProperty("id")]
public string Id { get; set; }
/// <summary>Gets or sets the guild ids the character is in.</summary>
[JsonProperty("guilds")]
public string[] Guilds { get; set; }
}
}when I wanted to pull information about it I did
using DangerBot.GW2.V2.Account.Rest;
using System.Threading.Tasks;
namespace DangerBot.GW2.V2.Account.Client
{
public partial class GW2ClientReduced
{
public async Task<Objects.Account> GetAccountAsync()
{
RestRequest restRequest = _client.Create("v2/account");
RestResponse<Objects.Account> restResponse = await restRequest.ExecuteGet<Objects.Account>().ConfigureAwait(false);
Objects.Account account = await restResponse.GetDataObject().ConfigureAwait(false);
return account;
}
}
}in practice:
var service = GW2.V1.Guilds;
var guild = service.FindByName("The Zone of Danger");
// Too lazy to convert v2 responce to GUID...
var guildId = guild.GuildId.ToString().ToUpper();
var gw2CustomClient = new GW2ClientReduced(e.GetArg("api-key"));
var account = await gw2CustomClient.GetAccountAsync();
if (account.Guilds.Contains(guildId))
{
// blah
}
it's actually really bad
it's just 3 classes and an enum now
normally images show :O
I don't understand the question :)
avoid System.Web if you're not creating a web application
by web app I mean website
And I've seen much worse
Written much worse, too 😂
@/all Sorry, for not writing anything in the last month or so. Preparation for exams, which come up the next three weeks have been particular stressfull this semester. But I looked at the current HttpClient branch and saw that it's nearly finished. There are some bugs to iron out, but nothing major. So if anyone is interested, he can take over.
Some things to note: Converter structure has been left almost entirely intact, so nothing to do here and I don't want to touch it until we got the underlying system robust enough. I have some ideas how we can throw most of the code out of the window. Most of it deals with JSON.Net (there's really no reason anymore, to not use it as default) and it's internal parser (it uses Attributes, which @StevenLiekens doesn't like, but if it makes better code, I'm willing to use it).
The new repository structure is entirely the same for "standard" api endpoint layout, so a user only has to implement two interfaces and he's done. For anything else there needs to be a custom interface describing the layout. That should be put into core obviously.
That's it basically. I'll try to read more often here, so if there are questions just ask.
I don't have the motivation to work on it right now
Maybe things get better in my new job
Why .netstandard?
after we implemented HTTP client ofc
{
"version": "1.0.0-*",
"compilationOptions": {
"emitEntryPoint": true
},
"resource": [
"fakedata.json"
],
"dependencies": {
"Microsoft.AspNet.IISPlatformHandler": "1.0.0-rc1-final",
"Microsoft.AspNet.Owin": "1.0.0-rc1-final",
"Microsoft.AspNet.Server.Kestrel": "1.0.0-rc1-final",
"Nancy.Linker": "0.3.0"
},
"commands": {
"web": "Microsoft.AspNet.Server.Kestrel"
},
"frameworks": {
"dnx451": {
"dependencies": {
"Nancy": "1.4.3",
"Nancy.Owin": "1.4.1"
}
}
},
"exclude": [
"wwwroot",
"node_modules"
],
"publishExclude": [
"**.user",
"**.vspscc"
]
}var assembly = Assembly.GetExecutingAssembly();
var resourceStream = assembly.GetManifestResourceStream("MyNamespace.fakedata.json");
using (var reader = new StreamReader(resourceStream, Encoding.UTF8))
{
return reader.ReadToEnd();
}
Or did you mean something different?