Skip to main content
Developer tools give Jefes access to a live debug console and backend data migration utilities. These tools are intended for platform administrators managing the GPSpedia backend.

Access

Developer tools are available to users with the Jefe role only. Look for Desarrollador in the side navigation menu. This option is not visible to Supervisor or Tecnico users.

Opening developer tools

1

Open the side menu

Click the menu icon to expand the side navigation panel.
2

Click Desarrollador

Click Desarrollador in the side menu. The Developer Tools modal will open.

Debug console

The debug console is a floating terminal window that displays real-time JavaScript debug logs from the running application. It uses a green-on-dark terminal style for readability.

Console controls

  • Clear — Clears the current log output from the console display.
  • Close — Closes and hides the floating console window.
The debug console window is moveable and resizable. Click and drag the title bar to reposition it on screen, and drag the edges or corners to resize it. This lets you monitor logs while interacting with other parts of the app.

Migration actions

The migration section contains utilities for updating data formats in the Google Sheets backend. Each migration is a one-time operation that transforms existing records to a new data structure.

Available migrations

Migrar Rangos de Años

Migrates year range data to the current format used by the catalog. Run this after updating the year range schema for vehicle records.

Migrar Timestamps

Migrates timestamp values across records to the current timestamp format. Run this when normalizing date/time storage across catalog entries.

Running a migration

1

Open Developer Tools

Click Desarrollador in the side menu.
2

Locate the migration action

Find the migration button in the Migration Actions section of the modal.
3

Click the migration button

Click Migrar Rangos de Años or Migrar Timestamps as needed.
4

Review the status

The tool displays a status message after execution indicating whether the migration succeeded or encountered an error.
Migrations modify data directly in the Google Sheets backend. They are not reversible through the UI. Before running a migration, confirm that you are operating on the correct environment and that the data format change is intentional. Running a migration more than once on already-migrated data may produce unexpected results.

Build docs developers (and LLMs) love