Add sleep/wakeup process to retrieve bucket data during plugin initialization

Abierto
#117 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
api, full-stack

Línea de trabajo

Start by comparing the sleep/wakeup flow in the referenced geowatch-agent-track implementation. Then trace the plugin descriptor's DATA_TO_RETRIEVE secureData, OFS bucket API calls, device cache/local storage, and plugin page entry point; the work is done when configured string and file properties are retrieved, persisted, displayed, and failure or missing-data cases are handled.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Enhancement Request

Overview

Implement a sleep/wakeup process similar to the geowatch-agent-track plugin that will invoke the OFS API during the plugin initialization to retrieve data from specified buckets.

Background

The geowatch-agent-track plugin (/Volumes/SSD Miquel - SanDisk/visual-code/cat-repos/geowatch-agent/geowatch-agent-track) demonstrates how to retrieve OFS position data during initialization. This enhancement will follow the same pattern but for retrieving bucket properties.

Requirements
Data Retrieval

The plugin should retrieve two types of properties from a specified bucket:

  1. String property - A text/string value stored in the bucket
  2. File property - A file stored in the bucket
Configuration

The bucket and properties to fetch will be defined in the plugin descriptor as secureData with the name DATA_TO_RETRIEVE in the following format:

[
    {
        "bucket_name": "my_data_bucket",
        "properties_to_fetch": {
            "string_property": "string",
            "file_property": "file"
        }
    }
]
Data Storage

After retrieving the data from the OFS API:

  • Store both the string property and file property in the device cache/local storage
  • Persist the data so it's available when the plugin opens
Data Display

When the plugin is opened:

  • Retrieve the previously stored data from device cache/local storage
  • Display both the string property value and the file property on the page
  • Handle cases where no data has been retrieved yet
Implementation Pattern
  • Follow the same sleep/wakeup pattern used in geowatch-agent-track
  • Invoke OFS API during plugin initialization (init process)
  • Handle both string and file property types
  • Store retrieved data in device cache/local storage
  • Display stored data when plugin opens
Technical Approach
  1. Add sleep/wakeup event handlers
  2. Parse DATA_TO_RETRIEVE from secureData
  3. Make API calls to OFS bucket API during initialization
  4. Handle string property retrieval
  5. Handle file property retrieval
  6. Store data in device cache/local storage
  7. On plugin open, retrieve data from local storage
  8. Display retrieved data on the plugin page
  9. Handle errors gracefully (missing bucket, properties, API failures, storage failures)
Reference Implementation

See: /Volumes/SSD Miquel - SanDisk/visual-code/cat-repos/geowatch-agent/geowatch-agent-track

Acceptance Criteria
  • Plugin reads DATA_TO_RETRIEVE configuration from secureData
  • Sleep/wakeup process initializes on plugin load
  • API calls retrieve string property from specified bucket
  • API calls retrieve file property from specified bucket
  • Retrieved data is stored in device cache/local storage
  • Plugin displays stored string property when opened
  • Plugin displays stored file property when opened
  • Handle cases where no cached data exists yet
  • Error handling for missing/invalid configuration
  • Error handling for API failures
  • Error handling for storage access failures
  • Documentation updated with configuration examples
Lenguaje dominante
TypeScript
Estrellas
6
Forks
5
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de oracle-samples/ofs-sample-plugins

Todos los issues de oracle-samples/ofs-sample-plugins

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.