Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 20 2019 08:19

    lingobot-development[bot] on lingobot-onboarding

    (compare)

  • Sep 20 2017 02:11

    waltfy on develop

    Update README.md (compare)

  • Nov 15 2016 17:24
    mattkrebs opened #19
  • Sep 03 2016 14:05

    waltfy on develop

    Add API key to examples Fix typos in `membershipType` Consistently require module in … and 1 more (compare)

  • Sep 03 2016 14:05
    waltfy closed #16
  • Sep 03 2016 14:04

    waltfy on v0.6.0

    (compare)

  • Sep 03 2016 14:04

    waltfy on develop

    Web release v0.6.0 Release v0.6.0. (compare)

  • Sep 03 2016 13:55

    waltfy on develop

    Adding new endpoints for Guardi… Merge pull request #18 from das… (compare)

  • Sep 03 2016 13:55
    waltfy closed #18
  • Sep 02 2016 13:14
    dasilva333 edited #18
  • Sep 02 2016 13:14
    dasilva333 opened #18
  • Jun 19 2016 15:59
    CMTegner opened #17
  • Jun 19 2016 15:42
    CMTegner opened #16
  • Jun 09 2016 07:16
    gugahoi opened #15
  • May 02 2016 13:01

    waltfy on fix-x-api-header

    (compare)

  • May 02 2016 13:01

    waltfy on master

    (compare)

  • Feb 07 2016 17:49

    waltfy on develop

    Update README.md Small typo. =) Merge pull request #14 from znj… (compare)

  • Feb 07 2016 17:49
    waltfy closed #14
  • Jan 30 2016 00:01
    znja opened #14
  • Oct 24 2015 19:30

    waltfy on develop

    fixes to README (compare)

Walter Carvalho
@waltfy
do you see the difference? The reason using localhost works on your development environment – say – is because you're under the same domain.
so when you're in http://apps.kevinashaffer.com/destiny, you'l have to hit http://apps.kevinashaffer.com:9000 as your host for the client
does that make sense?
kevinshaffer
@kevinshaffer
Yes, that was the problem, I was using localhost instead of that when making my initial call to your destiny method. Thank you for being so patient :) and for making something awesome
Walter Carvalho
@waltfy
yes.
It's ok. I was really puzzled for a second as to why it work, but you were right. At first your page was pointing at my actual proxy server.
Glad it is fixed now!
kevinshaffer
@kevinshaffer
Me too, thanks again!
Walter Carvalho
@waltfy
Using something like a configuration file will help you: something that loads some config dynamically, so that you don't have to worry about replacing it every time. But that's something for the future I guess, have fun building whatever you are making! I'd be keen to hear more about it.
Let me know if you want anything added to it too! Cheers @kevinshaffer
Baris Balic
@barisbalic
@waltfy we can remove the need for it altogether eventually.
Walter Carvalho
@waltfy
@barisbalic yup, I meant for the future of Kevin's app.
Baris Balic
@barisbalic
+1
Walter Carvalho
@waltfy
But yes, once we have a centralised service. A client ran proxy server wouldn't be necessary at all. ;)
kevinshaffer
@kevinshaffer
@waltfy Once it's something more than a pet project of me learning Bungie's API i'll be sure to share it :) And with this working I'll actually be able to get useful data rather than what the www.bungie-platform.herokuapp.com calls gives me
Walter Carvalho
@waltfy
@kevinshaffer ha yeah!
Baris Balic
@barisbalic
I tried adding you to the room, but was told you don't have permission, assuming you can join it
Walter Carvalho
@waltfy
Awesome.
@barisbalic player.io?
Baris Balic
@barisbalic
Indeed
Walter Carvalho
@waltfy
Not sure if I accepted the invite yet.
Baris Balic
@barisbalic
That would explain it
Walter Carvalho
@waltfy
I have now.
Pretty sweet, I see you've put some time into it already! Nice.
Sean Clayton
@sean-clayton
A little confused—so is this a client or an API wrapper in JS?
Baris Balic
@barisbalic
WHats the difference between a client and an API wrapper?
Sean Clayton
@sean-clayton
an API wrapper essentially translates an existing API
to make it more syntactically easier to use with a language, usually
a client is basically an API that's user-facing, essentially I think?
Baris Balic
@barisbalic
I think I'd classify all clients as API wrappers
but I get what you are saying
Baris Balic
@barisbalic
In either case it's something of a client
Walter Carvalho
@waltfy
@sean-clayton are you talking about client as an User Interface? If so this is not it. What this is, is just a library in which its API provides a mapping to Bungie's Destiny API End Points.
Also from my understanding, all APIs are user facing? That's just what they are, a programming interface to another program/library?
Thomas Heinrichsdobler
@fucx
If I were trying to integrate the Destiny API into hubot, would your client be a good starting point? please excuse my newbie question, I'm fairly new to node.
Baris Balic
@barisbalic
@fucx yeah it's a reasonable place to begin, you could try to hit the main bungie APIs directly, but they are a mess, waltfy/destiny cleans up the responses and makes it all easier to understand
Thomas Heinrichsdobler
@fucx
thanks @barisbalic , that's my first impression of the Bungie APIs as well. I'll give it a try, then. Thank you!
Baris Balic
@barisbalic
@fucx no problem mate, we've got some plans in the works that might make things even easier so stay involved!
Thomas Heinrichsdobler
@fucx
alright, looking forward to it!
Walter Carvalho
@waltfy
@fucx hey, yeah seems reasonable. Let me know if you get stuck on anything. I've recently done a rewrite of the whole library some stuff may be broken.
mart2967
@mart2967
Hi everyone! I'm trying to use this library in a react native app, and have run into some trouble right out of the gate. When calling destiny.Search there is no data returned, and no error either.
Here's the code:
componentDidMount: function() {
        console.log('searching');
        destiny.Search({
            membershipType: 2,
            name: 'mypsn'
        }).then(res => {
            this.setState({'user': res});
            console.debug('user', res);
        }).catch(err => {
            this.setState({'error': err});
            console.debug(err);
        });
    }
mart2967
@mart2967
I moved the logs above the setState, and now I get a TypeError: Network request failed. That's certainly better :)
mart2967
@mart2967
After removing the proxy server from the require, it works! Thanks for all the help haha (this seems to happen a lot, solving an inscrutable problem immediately after seeking assistance)
Walter Carvalho
@waltfy
@mart2967 hi, sure — let us know if you have any other issues
baaronp7
@baaronp7
Hello Walter I am building my own node.js destiny site. Just wondering how you did user authentication. Did you come up with an automated way of getting the bungie user cookie?
P.S. Here is my site and github link if anyone is interested...