Skip to content

Fixes #8: Restage Projects when Script Files are enabled or disabled - #48

Merged
jnovinger merged 1 commit into
mainfrom
8-disabling-a-script-file-through-its-edit-page-or-rest-does-not-restage-the-project
Oct 20, 2026
Merged

jnovinger merged 1 commit into
mainfrom
8-disabling-a-script-file-through-its-edit-page-or-rest-does-not-restage-the-project

Conversation

@pheus

@pheus pheus commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator

Fixes: #8

Restage the Project when a Script File is enabled or disabled through its edit page or the REST API. Require Project change permission, matching the Project's Script Files tab, and queue one refresh per Project for bulk updates.

Add regression tests and update the permission documentation.

@pheus
pheus requested a review from jnovinger October 20, 2026 17:11
@pheus
pheus marked this pull request as ready for review October 20, 2026 17:11
Apply the Project's selection rules to Script File edits in the UI and
REST API, including bulk updates. Changing enabled requires Project
change permission and queues one refresh per Project.

Add regression tests and update the permission documentation.

Fixes #8
@pheus
pheus force-pushed the 8-disabling-a-script-file-through-its-edit-page-or-rest-does-not-restage-the-project branch from aa21297 to b36d938 Compare October 20, 2026 18:12
@jnovinger
jnovinger merged commit f19850f into main Oct 20, 2026
20 checks passed
@jnovinger
jnovinger deleted the 8-disabling-a-script-file-through-its-edit-page-or-rest-does-not-restage-the-project branch October 20, 2026 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Disabling a Script File through its edit page or REST does not restage the Project

2 participants