Skip to content

Disable some jdd actions on closed ca#4037

Open
christophe-ramet wants to merge 2 commits intodisallow_update_delete_on_closed_affrom
disable_some_jdd_actions_on_closed_ca
Open

Disable some jdd actions on closed ca#4037
christophe-ramet wants to merge 2 commits intodisallow_update_delete_on_closed_affrom
disable_some_jdd_actions_on_closed_ca

Conversation

@christophe-ramet
Copy link
Copy Markdown
Contributor

@christophe-ramet christophe-ramet commented Apr 1, 2026

closes #3966

Il n'est plus possible de réactiver un JDD lié à un CA fermé, ni de modifier son CA d'origine si il est déjà fermé.

@christophe-ramet christophe-ramet marked this pull request as draft April 1, 2026 09:35
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 1, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.49%. Comparing base (92fa7a8) to head (b59e552).

Additional details and impacted files
@@                           Coverage Diff                           @@
##           disallow_update_delete_on_closed_af    #4037      +/-   ##
=======================================================================
+ Coverage                                86.47%   86.49%   +0.01%     
=======================================================================
  Files                                      137      137              
  Lines                                    10876    10891      +15     
=======================================================================
+ Hits                                      9405     9420      +15     
  Misses                                    1471     1471              
Flag Coverage Δ
pytest 86.49% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@christophe-ramet christophe-ramet force-pushed the disable_some_jdd_actions_on_closed_ca branch from 2107fb0 to b59e552 Compare April 1, 2026 14:30
Now check if AF is closed or not (so we don't let modify AF or active status). Little fix so we don't call twice the route for listing af.
@christophe-ramet christophe-ramet changed the base branch from develop to disallow_update_delete_on_closed_af April 1, 2026 14:37
@christophe-ramet christophe-ramet marked this pull request as ready for review April 1, 2026 14:38
Copy link
Copy Markdown
Contributor

@jacquesfize jacquesfize left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

J'ai bien une bad request quand j'essaie de modifier le statut d'un JDD dans un CA fermé.

Par contre, quand j'essaie de faire l'action j'ai un toaster avec une erreur pas compréhensible
Image

et le spinner qui continue de tourner

Image

Il faut remplacer le contenu du toaster avec un message explicite et enlever le spinner quand la modification échoue du statut d'un JDD échoue. Voir tout simplement, désactiver le bouton de changement de statut (en plus du bouton "Editer d'ailleurs)

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.

Rendre impossible la réactivation d'un JDD dont le CA parent est fermé

2 participants