-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FirebaseObjectFactory query option not used #706
Comments
The "Querying" section of that doc explains why queries would not be useful for object observables. Perhaps summed up best by: |
@katowulf So, should the option be removed? |
@katowulf And what, exactly, does this mean?
|
Sounds like a word puzzle. Maybe there's an easter egg? : ) |
@katowulf Would you welcome a PR that removes the unused imports and option or logs a not-implemented/supported warning? If so, which one? BTW, using the |
An initial guess is that it's probably best to remove the unused imports and clean up or maybe remove the docs section as well. But I haven't looked at the code to verify they are superfluous or that they aren't intended to be added later (unlikely). |
The docs mention that lists should be used for querying/filtering and the query option is ignored by the object factory. The query option should be removed so that it is no longer suggested by TypeScript-based tools, etc. Closes angular#706
Version info
Angular: N/A
Firebase: N/A
AngularFire: 2.0.0-beta.6
Expected behavior
The documentation for
FirebaseObjectObservable
suggests that thequery
option can be used.Actual behavior
The query-related imports and the
query
option are not used in theFirebaseObjectFactory
implementation, so any specifiedquery
option is ineffectual.It's not clear whether it's the source or the documentation that's out of date. Either the
query
option should be implemented (or should log a not-implemented warning, perhaps) or the documentation and source should be updated to reflect that thequery
option cannot be used with theFirebaseObjectObservable
.The text was updated successfully, but these errors were encountered: