Michaël Krens
Michaël Krens
I think this is a bug and should work: `me & you`. It get's extracted but not translated. But... if I add `me & you` and also extract and translate...
How do we feel about making a release for firebase v9 using the `firebase/compat` import? https://firebase.google.com/docs/web/modular-upgrade#update_imports_to_v9_compat This would unblock v9 upgrades. Funny enough, even the google project [firebaseui has done...
Made a [branch here](https://github.com/michi88/vuefire/commits/firebase9-compat) that can be installed like this in package.json: ``` "firebase": "^9.8.2", "vuefire": "github:michi88/vuefire#firebase9-compat" ``` You then need to add this `postinstall` is in your scripts sections...
@posva could you please let me know if you'd consider releasing a firebase 9 compat version? Because if not, I'll consider releasing separate npm packages as I need this in...
@posva could you please let me know, as else I'll release and publish a fork that is compatible with firebase 9. Thanks!
I agree we should change the implementation of this. What might work for you is use `static` without the trailing slash. Be aware that this will exclude *all* folders that...
We're using `copytree(site_packages, temp_package_path, symlinks=False, ignore=shutil.ignore_patterns(*excludes))` now. The problem with `ignore=shutil.ignore_patterns` is that it matches the current file or directory names on iteration and not the full path. This is...
Starting from zappa==0.40.0 the default role name has changed with the project env lambda name prepended: ``` { "Effect": "Allow", "Action": [ "iam:PassRole", "iam:CreateRole" ], "Resource": [ "arn:aws:iam:::role/-ZappaLambdaExecutionRole" ] }...
This has caused a lot of time for me to debug (that the latest docker version is not up to date with the sources here). Maybe we should add this...