Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(dossier): enable refresh after update on more champs #9299

Merged
merged 1 commit into from
Jul 11, 2023

Conversation

tchak
Copy link
Member

@tchak tchak commented Jul 11, 2023

No description provided.

@tchak tchak requested a review from mfo July 11, 2023 09:19
@what-the-diff
Copy link

what-the-diff bot commented Jul 11, 2023

PR Summary

  • Addition of a new Method
    A new method named refresh_after_update? has been added to the file type_de_champ.rb. This method helps in deciding if a field needs to be refreshed after it has been updated.

  • Function of the New Method
    The new method contains a case statement, a form of conditional logic in programming that returns either true (meaning, the field needs to be refreshed after an update) or false (the field doesn't need to be refreshed after an update). This decision is made based on the type of field.

  • Refresh Strategy for Different Field Types
    Certain fields like EPCI, communes, multiple_drop_down_list, etc., are set to be refreshed after an update. On the other hand, fields such as address, annuaire_education, and carte are specified not to be refreshed.

  • Default Behavior
    For all other field types that are not explicitly mentioned, the default behavior is to refresh them after an update.

@tchak tchak added this pull request to the merge queue Jul 11, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 11, 2023
@tchak tchak added this pull request to the merge queue Jul 11, 2023
Merged via the queue into demarches-simplifiees:main with commit d9cefb4 Jul 11, 2023
@tchak tchak deleted the feat-refresh-champ branch July 11, 2023 13:55
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.

2 participants