https://firebase.google.com/docs/functions/config-env?hl=es-419
firebase functions:config:set gmail.email='someEmail' gmail.password='somePass'
const isUseEffect = (node) => node.callee.name === 'useEffect'; | |
const argumentIsArrowFunction = (node) => node.arguments[0].type === 'ArrowFunctionExpression'; | |
const effectBodyIsSingleFunction = (node) => { | |
const { body } = node.arguments[0]; | |
// It's a single unwrapped function call: | |
// `useEffect(() => theNameOfAFunction(), []);` | |
if (body.type === 'CallExpression') { |
{ | |
"Statement": [ | |
{ | |
"Action": [ | |
"apigateway:*", | |
"cloudformation:CancelUpdateStack", | |
"cloudformation:ContinueUpdateRollback", | |
"cloudformation:CreateChangeSet", | |
"cloudformation:CreateStack", | |
"cloudformation:CreateUploadBucket", |
https://firebase.google.com/docs/functions/config-env?hl=es-419
firebase functions:config:set gmail.email='someEmail' gmail.password='somePass'
Hi, I am a fork from https://gist.github.com/patrickhammond/4ddbe49a67e5eb1b9c03.
A high level overview for what I need to do to get most of an Android environment setup and maintained on OSX higher Catalina and Big Sur with and without Android Studio been installed.
Considering the SDK is installed under /Users/<your_user>/Library/Android/sdk folder which is the Android Studio preferred SDK location, but it works fine under /usr/local/share/android-sdk as well, which is a location pretty much used on CI mostly.
https://github.com/shyiko/jabba instead ?
I made a list of 20 things I might want out of a monorepo tool for a Design System to use as a basis for comparing some of the options including Lerna, Northbrook, and Rush.
### Title options: | |
- GraphQL hoje para aplicações client-side que ainda dependem de APIs REST. | |
- GraphQL today using Apollo for applications that still depend on REST apis | |
- Wrapping REST apis with GraphQL using Apollo stack | |
# GraphQL today using Apollo for applications that still depend on REST APIs | |
Even though people using GraphQL are often extremely excited about the technology, it's popularity is [still growing slowly](https://trends.google.com/trends/explore?date=2014-03-14%202017-03-14&q=GraphQL). Developers working on client-side applications are the ones to benefit more from GraphQL, but migrating a backend from a working REST API might not be economically justifiable for most teams. What most don't realize, though, is that it is not completely necessary to make the switch on both sides before adopting the technology. The main [JavaScript implementation](https://github.com/graphql/graphql-js) of a GraphQL server runs just fine on the browser, and [Apollo](http://www.apollodata.com/) makes it easy a |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 29 Jul 2015 01:52:41 GMT till Fri, 29 Jul 2016 01:52:41 GMT.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter(user => user.followers > 6)