Settings and activity
38 results found
-
13 votes
Ruben Heymans supported this idea ·
-
4 votes
-
2 votes
An error occurred while saving the comment -
195 votes
-
2 votes
-
23 votes
-
19 votes
-
13 votes
-
99 votes
An error occurred while saving the comment I was hoping this would be prio, this combo removes almost all reasons not to use Firebase, most arguments on why not to use Firebase vs whatever (e.g. supabase) would not be valid anymore
-
24 votes
-
121 votes
-
88 votes
-
31 votes
An error occurred while saving the comment @Lars is that even possible?
An error occurred while saving the comment I can't post links but angularfire issue `Question about the future plans/maintenance of angularFire #3446` is related
An error occurred while saving the comment response from Firebase support:
Hi Ruben,
Thank you for sharing this feedback with us.
I truly understand the current dilemma right now for most developers regarding Firebase not officially supporting yet the AngularFire framework, and the possibility that their current plugins may not be fully aligned with our up-to-date version of our Firebase SDKs.
The current state of AngularFire right now being a third party framework is due to the fact that its libraries and resources are maintained by a third party developer group. Troubleshooting any issues or rolling out bug fixes related to AngularFire are being done by the developers there. Right now, this is the only official GitHub repository of the AngularFire development group that maintains this library. If you have any feedback or bug report directly on the AngularFire library, filing an issue in this tracker is the only way to go.
While we're not limiting the developers from using third party integrations like AngularFire, internal discussions toward our goal to officially support Firebase + Angular integration are still ongoing. I'd love to say more about this, but unfortunately, we don't have much information or timeline to share that would guarantee its release in the near future.
As an action item here, I'll be linking your ticket in our internal feature request discussion so that your feedback may serve as an upvote in hopes that we could get Firebase + Angular officially supported in the future. I truly appreciate your honest opinion on the way AngularFire stands right now and I want to let you know that your feedback here is something we truly value.
Let me know if there's anything else I can help you with.
Thanks,
Kyle -
3 votes
-
3 votes
-
2 votes
-
240 votes
Hi folks, this is being actively worked on, and is expected to preview sometime in H1 2024. Thank you for using UserVoice to help us prioritize!
An error occurred while saving the comment good news , I hope we can also use it with angularfire soon after release
-
24 votes
-
9 votes
-
63 votes
The more features they add, the more complex it becomes. I do agree that it can become confusing at times, particularly when using it in combination with Angular.
Is there anything specific you're stuck with, I could try and help you out? (in Dutch?)
The unexpected large bill has an open issue here on uservoice (Allow setting a maximum amount per billing cycle). But I do agree that it's weird it's not implemented already. There is also an extension now that can disable your billing once it reaches a certain amount.