[Bug] Databases.CreateDatabaseRequest and CreateCollectionRequest defaults Enabled to false

[AngryAnt]

Describe the bug

Databases.CreateDatabaseRequest and CreateCollectionRequest defaults Enabled to false. So the API logic is currently that if you don't specify anything, you probably want your new thing to be disabled.

It is a bit hard to follow that logic, so I am assuming it is unintentional. Especially since the Appwrite cloud interface does not show you that a database or collection is disabled. You have to know that the reason you can populate a collection via the server API and the web UI, while you keep hitting "database not found" when attempting the same on the client API is indicative of this state.

The Appwrite team did not immediately know this which is why they just spent a week with me trying to find out how I had somehow managed to mess up my client code ;)

Reproduction Steps

await databases.CreateDatabase (new CreateDatabaseRequest
{
	DatabaseId = kDatabaseID,
	Name = kDatabaseName
});

2. The database appears normally in the web UI and can be populated via the server API just fine.
3. Access to the database via client API will fail with a "database not found" error, while realtime updates from edits made via server API or the web UI will go through to the client just fine.

Expected Behaviour

The API assumes that unless otherwise specified, the new thing you are creating is something you want enabled.

Screenshots / Examples

No response

.NET version

No response

Additional Context

No response

[pingu2k4]

On it