🔖 Feature description

Not 100% sure if there currently is a way to deal with this (or what is the right way, this might not be a feature and rather an issue) however...

If we have a function that listens 3 levels deep on a database, all being wildcards for e.g:
databases.*.collections.*.documents.*.create

The idea is to be able to access the event data of which currently we can for the collection ID and document ID since that data is embedded, but not in the case of database ID. Is this an oversight or?

When using wildcards, obviously this event data is unknown until the event occurs therefore, we'd want to filter it not partially, but to include all properties that have wildcards on them, including database ID.

Since the introduction of databases in 0.15.0 - The only way I've seen to access the database ID for an event is on the APPWRITE_FUNCTION_EVENT env var where the string looks like this:
databases.DATABASEID.collections.COLLECTIONID.documents.DOCUMENTID.create

I'm performing a string split on this to extract the databaseId but this feels super clunky, let alone whether it's a trustable source?

I asked on Discord and it was mentioned to use a hard coded const in the code of the function. But then what would be the point of listening to events with wildcards if we can't filter that data? The database ID simply cannot be known and since we now have the ability to have multiple databases, we should be able to filter that too.

🎤 Pitch

A more official way to access the database ID on function events.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct