You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The directory for Firebase extensions manifest is currently hardcoded as "extensions". This restricts flexibility for users who want to organize their project structure differently, especially in monorepos or more complex setups where Firebase configs are grouped in specific directories.
In many cases, it would be beneficial to have the ability to specify the directory for Firebase extensions in the firebase.json configuration file, just like how we can specify paths for Firestore rules, indexes, storage rules, and other Firebase-related configurations.
The directory for Firebase extensions manifest is currently hardcoded as
"extensions"
. This restricts flexibility for users who want to organize their project structure differently, especially in monorepos or more complex setups where Firebase configs are grouped in specific directories.In many cases, it would be beneficial to have the ability to specify the directory for Firebase extensions in the firebase.json configuration file, just like how we can specify paths for Firestore rules, indexes, storage rules, and other Firebase-related configurations.
Code Reference
firebase-tools/src/extensions/manifest.ts
Line 16 in 3e84ee8
The text was updated successfully, but these errors were encountered: