You can read more about it here: https://www.bitovi.com/blog/join-us-for-our-first-online-meetup
Here’s where you can save your spot: https://zoom.us/meeting/register/0f9a68cba6f5846e66858a512be5123a
Also, we’re now on Slack too! I posted about it on our forums: https://forums.donejs.com/t/you-re-invited-to-bitovi-s-community-slack/1018
You can join the Slack here: https://tinyurl.com/BitoviCommunitySlack
@CrusaderJellyfish I don’t think I’ve seen anything with Firebase auth, just the CDN https://donejs.com/Guide.html#set-up-firebase
Today’s the last day to vote in our latest community survey! 🗳 https://www.surveymonkey.com/r/bitovi-feb-2019
Join our first online meetup now! 🎉 We have a great lineup of speakers on topics including Chrome extensions, Velocirender, DevOps, and recursive React components.
Register here: https://zoom.us/meeting/register/0f9a68cba6f5846e66858a512be5123a
Join here: https://zoom.us/j/351415253
like closing a dropdown menu when someone clicks off of it?
that would close the dropdown
just do it in the
connectedCallback of the component
this shows it actually: https://canjs.com/doc/guides/logic.html#OrganizeViewModelproperties
you can put the window listener in the property itself
that's the way to go @CrusaderJellyfish
Our next online meetup is going to be on Thursday, March 21st! Register here and check out the videos from our last meetup: https://www.bitovi.com/blog/save-the-date-march-21st-for-our-next-online-meetup-and-videos-from-februarys-meetup
is there a way to turn off caching?
even if its just at the level of specific attributes?
What’s an example of the app init promises… fetching configuration or something like that?
BTW almost everyone’s moved to our Slack: https://www.bitovi.com/community/slack
You’ll get a response from more people there :D
I wrap a promise around the call that checks if the session is still active
and without fail, the promise, initially loads as resolved so matter what I try, since that was its last state before reload, and when it kicks off again, it triggers the update
So, {{ fb_promise.isResolved }} is always true no matter what I do unless I add it as a new attribute (or change its name), and then the very first time it loads, it 'isPending' once. When the promise resolves each subsequent time again (the .then is triggered), it hits the code as it should.
Since I can toggle the name of the attribute and it isn't hitting the problem, I'm leaning towards it being a caching issue
I found an example in the recipes of using Google Youtube auth a similar way. I'll have to compare how I'm doing it with Firebase with how its written for that, but in the mean time ... is there no way to turn off client side caching?
its just a wrapper around Firebase's API code itself
Thanks!
…and yup, happy to help!
