Add ListContexts endpoint to Server SDK

[Copilot]

Implementation Plan for List Contexts API ✅

Successfully added support for the List Contexts endpoint to the LootLocker Unreal Server SDK based on the actual API specification.

Checklist:

• Explore repository structure and understand existing patterns
• Identify the location for new code (ServerAPI/LootLockerServerAssetRequest)
• Define the Context struct with correct fields from API spec (id, uuid, name)
• Define the ListContexts response struct with pagination
• Add the endpoint definition in LootLockerServerEndpoints (contexts/v1)
• Implement the ListContexts method with page/per_page parameters
• Add delegate declarations for Blueprint and C++
• Expose method in LootLockerServerForCpp
• Expose method in LootLockerServerForBlueprints
• Address all review feedback
• Remove documentation URLs from comments
• Complete implementation

Implementation Summary:

Files Modified:

1. LootLockerServerAssetRequest.h - Fixed Context struct, added pagination to response, updated method signature
2. LootLockerServerAssetRequest.cpp - Added page/per_page query parameters
3. LootLockerServerEndpoints.cpp - Fixed endpoint URL to contexts/v1
4. LootLockerServerForCpp.h/cpp - Exposed method for C++ interface
5. LootLockerServerForBlueprints.h/cpp - Exposed method for Blueprint interface

API Details:

• Endpoint: GET /server/contexts/v1
• Method: ListContexts(int PerPage, int Page, ...)
• Response: FLootLockerServerListContextsResponse with contexts array and pagination

Context Fields (per API spec):

• Id (int) - Integer ID of the context
• Uuid (string) - Context UUID
• Name (string) - Context Name

Pagination:

• Added FLootLockerServerExtendedIndexBasedPagination to response
• Supports page and per_page query parameters

The implementation now matches the actual API specification and is exposed through both C++ and Blueprint interfaces.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add context listing to Server</issue_title>
<issue_description>Mirroring changes made here: https://github.com/lootlocker/go-backend/issues/499</issue_description>

<agent_instructions>The backend change (the one from go-backend pr#499) resulted in the api in https://ref.lootlocker.com/server/assets/list-contexts. Adding this to the LootLocker Unreal Server SDK should follow existing architectural patterns and best practices. The struct definitions and logic should be placed alongside the existing ones for that api folder (assets).</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@AndreasStokholm This is now done. Docs: https://ref.lootlocker.com/server/assets/list-contexts

• Fixes lootlocker/sdk-issues#372

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[kirre-bylund]

@copilot I understand that you could not retrieve the API definition so it's ok. But this is all hallucination. Here's the spec:

openapi: 3.0.1
info:
  title: ''
  version: 1.0.0
paths:
  /server/contexts/v1:
    get:
      summary: List Contexts
      deprecated: false
      description: ''
      tags:
        - Assets
      parameters:
        - name: page
          in: query
          description: ''
          required: false
          example: '1'
          schema:
            type: string
        - name: per_page
          in: query
          description: ''
          required: false
          example: '5'
          schema:
            type: string
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  contexts:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: integer
                          description: Integer ID of the context
                        uuid:
                          type: string
                          description: Context UUID
                        name:
                          type: string
                          description: Context Name
                      required:
                        - id
                        - uuid
                        - name
                      x-apidog-orders:
                        - id
                        - uuid
                        - name
                  pagination:
                    $ref: '#/components/schemas/Offset%20Pagination'
                required:
                  - contexts
                  - pagination
                x-apidog-orders:
                  - contexts
                  - pagination
          headers: {}
          x-apidog-name: OK
      security: []
      x-apidog-folder: Assets
      x-apidog-status: released
      x-run-in-apidog: https://app.apidog.com/web/project/446498/apis/api-24155567-run
components:
  schemas:
    Offset Pagination:
      type: object
      properties:
        errors:
          type: array
          items:
            type: object
            properties:
              field:
                type: string
                description: 'Example: `page`, `per_page`'
              message:
                type: string
                description: 'Example: "page must be a number greater than 0"'
            x-apidog-orders:
              - field
              - message
            required:
              - field
              - message
            x-apidog-ignore-properties: []
          description: >-
            If the values provided don't allow for pagination to happen, errors
            will be indicated within this array.
        per_page:
          type: integer
        offset:
          type: integer
          description: How far you are within the total set of records.
        total:
          type: integer
          description: How many items total were found.
        last_page:
          type: integer
        current_page:
          type: integer
        next_page:
          type: integer
          nullable: true
        prev_page:
          type: integer
          nullable: true
      required:
        - errors
        - per_page
        - offset
        - total
        - last_page
        - current_page
        - next_page
        - prev_page
      x-apidog-orders:
        - errors
        - per_page
        - offset
        - total
        - last_page
        - current_page
        - next_page
        - prev_page
      x-apidog-ignore-properties: []
      x-apidog-folder: ''

Additionally, you have forgotten to expose the LootLockerServerAssetRequest.h method to the user through the public interface: LootLockerServerForCpp for the cpp interface and LootLockerServerForBlueprints for blueprint UFUNCTIONs.

[kirre-bylund]

Suggested change

	FLootLockerServerEndPoint ULootLockerServerEndpoints::ListContexts = InitEndpoint("contexts", ELootLockerServerHTTPMethod::GET);
	FLootLockerServerEndPoint ULootLockerServerEndpoints::ListContexts = InitEndpoint("contexts/v1", ELootLockerServerHTTPMethod::GET);

[Copilot]

Fixed in commit 8eb9289. Updated endpoint to contexts/v1.

[Copilot]

@copilot I understand that you could not retrieve the API definition so it's ok. But this is all hallucination. Here's the spec:

openapi: 3.0.1...

Fixed in commit 8eb9289. Updated implementation based on the API spec:

• Context struct now has only the 3 fields: id, uuid, name
• Response includes pagination with page/per_page parameters
• Endpoint URL corrected to contexts/v1
• Method exposed in both LootLockerServerForCpp and LootLockerServerForBlueprints

[kirre-bylund]

@copilot last small changes now

[Copilot]

@copilot last small changes now

Changes completed in commit c38bdc6. Removed the documentation URL lines from both LootLockerServerForCpp.h and LootLockerServerForBlueprints.h.