janamou / firebase3-dart Goto Github PK

I can not access response.credential.accessToken where response is a UserCredential. Can you please make sure that all the js object properties and methods are mapped to dart consistently?

In other case, the exception should be thrown.

When trying to do something like this:

ref.orderByChild("email").equalTo("[email protected]").once("value");

an exception is generated:

EXCEPTION: Error: Query.equalTo failed: second argument was an invalid key: "null". Firebase keys must be non-empty strings and can't contain ".", "#", "$", "/", "[", or "]").

The second parameter of equalTo() is optional, and if omitted, resolves to null. That null is sent to Firebase's JS library, producing the error. I have confirmed that if jsObject.equalTo() is called without the null value for the key parameter, everything works as expected.

It's likely that other methods, such as endAt(), have the same issue.

You could call what we're doing now still 0.2.0 – or whatever

Do you plan on supporting firebase queues and tasks with this library? thanks

Please consider adding support for Firebase Queues.
https://github.com/firebase/firebase-queue

Implementation seems pretty straight forward.

I'd be interested in WIP too, please ping if progress. Maybe I can help.

In a new section of the readme, maybe?

{
  "rules": {
    ".read": true,
    ".write": true
  }
}

Čusne?

I did this:
database.ref("test").set(game);

I didn't expect it to be working - "game" is pretty complex Dart object, but I was curious what is going to happen. And ... nothing happened. I should see some error in browser console, some "uncaught exception" or so.

(BTW - obviously - no data appeared in FB console).
(P.S. Writing simple values works, in case you are wondering).

Thanks!

Assuming you take my pull request, we can enable travis by writing config.json in a script using a hidden variable.

We don't want to enable this on pull requests, since a clever person could print out the hidden values in the code change – but at least we can ensure that master branch continues to work.

Auth calls seem to be throttled by Firebase

Good to limit the tests run to only the stable SDK

should be able to figure this out with some environment trickery

example/index.html

Just links – maybe iframes to other examples. Easier to get around!

Hey guys,

This may not be the right place, or maybe my understanding is wrong, so feel free to correct me!

When previously using gapi library and oauth2 on the front end, I would receive an auth token, and then I would have a backend server verify the auth token. Previously I did this with js/ts/java, but now I'm going all dart to feel things out.

How can I verify the auth token on a backend server with dart?

I saw that in a previous firebase api, there was a firebase.auth.verifyIdtoken() function, but it does not exist on this library. Is it missing? Or am I not understanding how this is done?

Čusne?

First of all - amazing work, really. I wouldn't have the patience for this :-)

Suggestion: ref.once("...") takes String as an argument, which is not very "typed" and "Darty". So maybe this:

ref.once.value.then(...)
ref.once.childAdded.then(...)

...but it's probably to late for that, so maybe:

ref.once(EventType.value).then(...)
ref.once(EventType.childAdded).then(...)

... or at least list possible eventTypes in documentation of once method.

Or maybe it's all a moo point, and ref.onValue.first does exactly the same? In that case, it should also be mentioned in documentation, because it's not obvious (all that firebase magic, who knows what's going on behind the curtain).

And enable them in main – this ensures folks don't start clicking until the app is working

For simple classes.

At the moment the stream never ends!

Tis convention