is project ID redundant?

[lawipac]

In this example,

    std::string apiKey = "<your-api-key>"; 

    Appwrite appwrite(projectId);

    // for the Databases instance
    Databases& databases = appwrite.getDatabases();
    databases.setup(apiKey, projectId);

the last line, Isn't it a duplication to ask for project ID again?

    databases.setup(apiKey, projectId);

In addition, for appwrite, the apikey is at project level, it would be logical to initialize it at client aka the class Appwrite

#just my 0.25 cents

Last but not least, finally, c++ SDK; kudos to the team!

[pooranjoyb]

First of all, we're so glad that you took your efforts to go through the SDK in the first place. This was basically a major project that me & @sristy17 we're building since last 3-4 months.

The main reason that we started this, was ofc, unavailability of SDK support of C++, so, we both thought of building it from scratch.
Now, coming back to your query, Yes, it is redundant, we should've inherited properties of the parent class while initializing other classes. We'll try fix these changes asap, but we're low on team-size.

We're looking for contributors (ofc if you're interested, please be interested, HELP US ://) as this is still in it's development phase.

@lawipac

[sristy17]

Yes, we would really appreciate your help.
@lawipac

[pooranjoyb]

Taken into account in #22