Unity client sdk

[Fellmonkey]

What does this PR do?

This PR adds comprehensive Unity SDK support to the SDK generator by:

1. Unity Language Implementation: Introduces a new Unity language class (src/SDK/Language/Unity.php) that extends the base Language class, providing Unity-specific type mappings, keywords, and code generation logic for C# in Unity environment.

2. Unity Template System: Adds a complete set of Unity-specific templates under templates/unity/Assets/ including:

   • Runtime components (Client, Services, Models, Enums, etc.)
   • Editor tools (Setup Assistant, Setup Window)
   • Unity project files (assembly definitions, project settings)
   • Required .NET libraries for Unity compatibility

3. Automated Testing Integration: Introduces Unity2021 test support with:

   • Unity2021Test.php test class that integrates with the existing test framework
   • Unity test source files (Tests.cs, Tests.asmdef) for comprehensive SDK testing
   • Docker-based Unity CI testing using unityci/editor:ubuntu-2021.3.45f1-base-3.1.0

4. CI/CD Integration: Updates the GitHub Actions workflow to:

   • Include Unity2021 in the test matrix alongside other SDK platforms
   • Set up the UNITY_LICENSE environment variable for Unity Editor automation
   • Enable automated testing of the Unity SDK in the CI pipeline

5. Unity Project Structure: Implements proper Unity package structure with:

   • Assets organized under Assets/Runtime/ and Assets/Editor/
   • Required Unity project settings and manifest files

Test Plan

The testing strategy includes:

1. Unit Testing: The Unity2021Test.php runs comprehensive tests covering:

   • HTTP operations (GET, POST, PUT, PATCH, DELETE)
   • File upload functionality with different file types
   • Error handling and exception management
   • OAuth2 authentication flow
   • Query helper methods
   • Permission and role management
   • ID generation utilities

2. Docker-based CI Testing: Tests run in a controlled Unity environment using:

   • Unity Editor 2021.3.45f1 in headless mode
   • Automated license activation using secrets
   • PlayMode test execution with filtered output
   • Integration with the existing mock API server

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

Yes

[Fellmonkey]

I am also attaching instructions on how to obtain a Unity license painlessly.
manual

[Fellmonkey]

The basic functionality tested in the test is guaranteed to work, but I'm not sure about the rest. I will continue to refine it.

Also, a question: What to implement next for the client SDK?

[Fellmonkey]

The test failed because the secret is not configured in appwrite/sdk-generator.

The successful test is here:
https://github.com/Comanda-A/sdk-generator-b/actions/runs/16206122996/job/45756699934

[Fellmonkey]

// Cookie support
client.SetCookie() / client.GetCookie()

// Real-time subscriptions  
realtime.Subscribe(channels, callback)

// Connection testing
await client.Ping()

The successful test is here:
https://github.com/Comanda-A/sdk-generator-b/actions/runs/16240261125/job/45855715029

[Fellmonkey]

Hello, @abnegate

• We have lots of duplication with the server-side .NET SDK, can we extend that instead?

Converters enum models extensions can be taken directly from dotnet (I don't think I changed anything). The rest of the files Id, Roles, etc.
The services can also be taken, but there is one difference with(Task -- UniTask). I don't have any ideas yet on how this could be implemented.

• We are targeting Unity 2021, which is now end-of-life. Can we move to 2022 LTS or even 6.0 LTS?

As I said in my reply to UniTask, I was developing a general solution, which also applies to Unity versions. It is possible to change the CI, but there is no point. I work with the SDK on Unity version 6 and there are no errors or warnings about using old methods.

• I couldn't see any code that handles navigating back into the game and storing the cookie from the OAuth path, can you point me to it?

I have a code locally, but I haven't tested it yet.

• Bit confused on how to set up the license. The instructions linked mention that it needs to be generated on the same machine that will run the tests, but that won't be the case if we generate with the linked action, set a repo secret, then run tests in a different action.

Yes, it's quite confusing. I found the official answer, which is easier to understand. The main thing is to run the script in any repository, get the .alf file (follow the instructions to get the .ulf file) and put the .ulf file in secret.

[Fellmonkey]

Hey, first of all, awesome work! Really appreciate the effort and attention to detail here. A couple more comments:

• We have lots of duplication with the server-side .NET SDK, can we extend that instead?

The Unity and DotNet SDKs use common elements from shared. The only difference is that each SDK has its own client. Also, necessary items for the client SDK.

I think I'll send this branch to PR when PR unity is accepted or in the near future (if dotnet is going to be changed, it will be done in shared).
Fellmonkey#9

[Fellmonkey]

OAuth functionality has been added and tested on Web and Android platforms.

While implementing this feature, I accidentally ended up creating a small Unity Playground, so you can now try out the functionality directly in your browser.

Repositories:

• SDK: https://github.com/Fellmonkey/sdk-appwrite-unity
• Playground: https://github.com/Fellmonkey/playground-appwrite-unity

[Fellmonkey]

In any case, it will be necessary to accept #1138 first as it synchronized Unity and DotNet in general.