Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Mar 24 18:06
    StevenLiekens commented #59
  • Mar 24 18:05
    StevenLiekens closed #59
  • Mar 24 18:05
    StevenLiekens commented #59
  • Mar 24 17:47
    StevenLiekens closed #58
  • Mar 24 17:47
    StevenLiekens commented #58
  • Mar 19 13:02
    Friesinator edited #59
  • Mar 19 13:01
    Friesinator opened #59
  • Mar 18 12:38
    StevenLiekens commented #58
  • Mar 15 15:19
    GHOSCHT commented #58
  • Mar 14 22:01
    Seeker1437 commented #58
  • Mar 14 20:08
    GHOSCHT commented #58
  • Mar 12 15:40
    StevenLiekens commented #58
  • Mar 10 15:46
    GHOSCHT opened #58
  • Apr 15 2018 16:43

    Ruhrpottpatriot on ServiceClient

    Remove superfluous compression … Add simple caching to Core proj… Move files into different folde… and 8 more (compare)

  • Apr 10 2018 21:09

    Ruhrpottpatriot on ServiceClient

    Add fluent api to create HttpRe… Fix Stylecop errors Remove dead code and 3 more (compare)

  • Mar 29 2018 13:11

    Ruhrpottpatriot on NetCore2.0

    Remove disabled and superseded … Delete unused leftover code fro… Move V1.Guild test to appropria… and 8 more (compare)

  • Mar 29 2018 12:17

    Ruhrpottpatriot on NetCore2.0

    Update .gitignore to exclude St… Add Api builder class (compare)

  • Feb 01 2018 09:33

    Ruhrpottpatriot on master

    Refactorize ServiceClient.GetHt… Merge pull request #57 from Kor… (compare)

  • Feb 01 2018 09:33
    Ruhrpottpatriot closed #57
  • Dec 27 2017 17:37
    Korjam opened #57
Steven Liekens
@StevenLiekens
oh
yeah no
have you played heart of thorns yet?
Robert Logiewa
@Ruhrpottpatriot
no
I should probably get it around christmas
Steven Liekens
@StevenLiekens
suppose that we get version 1.4 ready for all API patches released so far
what exactly do we still need to do to get version 2.0 ready?
I think we can postpone some of these issues
Steven Liekens
@StevenLiekens
fml
Steven Liekens
@StevenLiekens
I'm integrating patches from 1.4 into master now
Robert Logiewa
@Ruhrpottpatriot
good to hear
I'm finally back up on my feet. My cold was a bit more serious, that initially thought. However if 1.4 is release ready I'll publish it asap
Regarding 2.0
It will be a bit longer, since I want to incorporate the restructuring of the repositories
Steven Liekens
@StevenLiekens
1.4 is ready
it supports every HoT api patch to date
which is mostly just new item and recipe types
and revenant stuff of course
Steven Liekens
@StevenLiekens
@Ruhrpottpatriot does the new stylecop analyzer still use Settings.StyleCop files?
or is that for stylecop.exe only?
Steven Liekens
@StevenLiekens
fyi I don't work between dec 12 and jan 11
so I'll have tons of time to actually get stuff done
Robert Logiewa
@Ruhrpottpatriot

The new analyzers don't use the Stylecop files anymore. We have a set of rules that are either in the MS ruleset or the Stylecop rulesset. We then get two files which specify the disabled rules (and some other things).
However I'm seriously thinking about converting everything from portable csproj to xproj (i.e. ASP.NET5/vNext) since that is now in RC1. This would have many benefits for targeting multiple sets of .NET and a much easier version management (not in the Git sense) via the project.json files. Publishing to NuGet would be much easier too with these files.

But in the end I leaning towards a 2.0 release with portable csproj files and then a 3.0 for the new project system (since 1.0 of ASP.NET5 is scheduled for Q12016)

Steven Liekens
@StevenLiekens
sounds good
for me it's whatever
I just don't want to keep having to update old code for new game features
Robert Logiewa
@Ruhrpottpatriot
yeah I can understand that
Robert Logiewa
@Ruhrpottpatriot
damn, now that I know more about expression trees and IQueryable, I sort of want to implement it into GW2.NET...
Steven Liekens
@StevenLiekens
isn't the api too limited for what IQueryable can do?
Robert Logiewa
@Ruhrpottpatriot
not at all
the main benefit of IQuerable are Expressions and ExpressionTrees
Steven Liekens
@StevenLiekens
like how you can only query 200 ids at a time
and how you can't do an accurate .Skip() and .Take() because of how paging works
Robert Logiewa
@Ruhrpottpatriot
that is not a problem of IQueryable. Think of it as a possibility to construct lambdas and other expressions on the fly and then translate them into something else
you don't have to implement those methods
remember, those are extension methods
they are not built into the interface
ok
hm...
I need to get into this a bit more
but it should be possible
Steven Liekens
@StevenLiekens
items.Skip(49).Take(50)
can you?
I think you would have to do something like that
and then merge the collections
lol
it's definitely a challenge