Samir Boulahtit b39dd1251c fix: use consistent optional chaining for selectedJob in templates ...

Fix JavaScript TypeError "can't access property 'error_details',
selectedJob is null" by using optional chaining consistently.

Changed in all three templates:
- x-show="selectedJob?.error_details?.length > 0" (was missing ?. before length)
- x-text="JSON.stringify(selectedJob?.error_details, ...)" (was missing ?.)

Affected templates:
- app/templates/admin/marketplace.html
- app/templates/admin/imports.html
- app/templates/vendor/marketplace.html

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-12-05 21:59:32 +01:00

..

api

fix: admin import jobs API response format and background processing

2025-12-05 21:55:53 +01:00

core

feat: add logging, marketplace, and admin enhancements

2025-12-01 21:51:07 +01:00

exceptions

refactor: migrate vendor APIs to token-based context and consolidate architecture

2025-12-04 22:24:45 +01:00

routes

feat(admin): add Platform Administration section to sidebar

2025-12-03 23:01:26 +01:00

services

fix: correct service methods and add inventory schema model

2025-12-05 21:41:33 +01:00

tasks

refactor: modernize code quality tooling with Ruff

2025-11-28 19:37:38 +01:00

templates

fix: use consistent optional chaining for selectedJob in templates

2025-12-05 21:59:32 +01:00

utils

fix: protect critical re-export imports from linter removal

2025-11-28 20:10:22 +01:00

__init__.py

Refactoring code for modular approach

2025-09-09 21:27:58 +02:00