HSLG Media

WordPressVenueRepository.php

WordPressVenueRepository.php

Source file: wordpress/hslg-app-api/src/database/WordPressVenueRepository.php

Module: wordpress-hslg-app-api

Size: 28 lines

SHA-256: 49bfc92f71e4090ca33d8c254dad5f319980cb3c10c8364c10dea6d8c5f032ec

Responsibility

Hosts independently deployable HSLG-owned API endpoints and schema operations on WordPress/MariaDB.

Declared entry points

  • WordPressVenueRepository — source line 10.
  • __construct — source line 12.
  • all — source line 13.

Imports and dependencies

  • Line 4: use Hslg\Backend\Contracts\VenueRepository;
  • Line 5: use Hslg\Backend\Database\TableNames;

Behaviour and audit locations

Review control flow and returned values in the named source file; no special integration marker was detected.

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.