JavaScriptComponent's `status` must be respected by the

Created on 25 February 2025, 12 days ago

Overview

πŸ› Library includes components/blocks that have been disabled Active added detailed docs about how JavaScriptComponent's status should work, in docs/config-management.md, section 3.2.1.

But:

  • there's no test coverage yet to prove it actually works this way
  • from experience, @balintbrews and @hooroomoo know it doesn't work this way

Proposed resolution

  1. Add test coverage.
  2. Fix.

User interface changes

None β€” other than setting status: false on a code component now actually being respected, and this being reflected in what appears to the content creator.

πŸ› Bug report
Status

Active

Version

0.0

Component

Internal HTTP API

Created by

πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024