-
Notifications
You must be signed in to change notification settings - Fork 31
use console.log instead of context.log #36
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
Conversation
✅ Deploy Preview for private-cdn-edge-functions-examples ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for candid-travesseiro-824c81 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for edge-functions-examples ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for edge-functions-examples ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Thanks for this, @Skn0tt! Do we want to add some explainer text saying that you can use both |
From my understanding, there's no functional benefit in using |
I agree with @Skn0tt. |
I can go for that. Would you like to replace all mentions of |
I opened a tracking issue for deprecating |
I updated this PR so that it removes every mention of |
Yeah I'm good with this! |
Why can't I see this deploy preview, though? |
Not sure of the exact reason, but that contains |
Hmm that's weird — it's the deploy preview link provided by the PR! Anyway, looks good. Approved. And thank you! |
console.log has been equivalent to context.log for a while now, let's also show that in the examples.