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

[AntaresWeb] Study notes are not always saved in variants #1935

Closed
PPlessiez opened this issue Feb 15, 2024 · 3 comments · Fixed by #1959
Closed

[AntaresWeb] Study notes are not always saved in variants #1935

PPlessiez opened this issue Feb 15, 2024 · 3 comments · Fixed by #1959
Assignees
Labels
bug Something isn't working
Milestone

Comments

@PPlessiez
Copy link

PPlessiez commented Feb 15, 2024

Description

When a variant is created from an original study, if the user updates the notes of the variant, the modifications are not always taken into account: the modifications are overwritten by the original notes from the original study.

Provide a clear and concise description of the issue.

Steps to Reproduce

  1. Create a study with notes.
  2. Create a variant of this study.
  3. Update the notes of the variant and save them: a confirmation message appears.
  4. Leave the variant, then re-open it to check the notes.

Expected behavior

After step 4, the updated notes should appear.

Current behavior

After step 4, the updates of the notes have not always been saved: they have been replaced by the notes from the original study, even though the confirmation message that the notes have been saved appears in step 3.

@PPlessiez PPlessiez added the bug Something isn't working label Feb 15, 2024
@MartinBelthle
Copy link
Contributor

MartinBelthle commented Feb 29, 2024

When editing comments of a variant, it does not trigger a command.
It's written inside the variant folder next to the snapshot directory inside the patch.json file.
This is not a desirable behavior (also because in the long term we want to get rid of the patch.json file i believe).
Instead, what's need to be done is the following : Using the endpoint on a variant triggers a command : update_raw_file such as :

{
  "action": "update_raw_file",
  "args": {
      "target": "settings/comments",
      "b64Data": the data filled by the user
   }
}

@laurent-laporte-pro
Copy link
Contributor

laurent-laporte-pro commented Mar 1, 2024

Il y a des limitations concernant les variants et je pense que les notes en font partie, car celles-ci ne sont pas enregistrées dans l'historique des commandes. Il en est de même pour la configuration Xpansion.

@MartinBelthle
Copy link
Contributor

MartinBelthle commented Mar 1, 2024

How to reproduce 100% of the time:

  • Create a study
  • Create a variant of this study.
  • Update the notes of the variant and save them: a confirmation message appears.
  • Generate the variant using the Generation button (top right button with the flash sign next to it)
  • Once the generation is over, refresh the page and do anything you want, the comments disappeared.

@laurent-laporte-pro laurent-laporte-pro added this to the v2.17 milestone Mar 27, 2024
@makdeuneuv makdeuneuv modified the milestones: v2.17, v2.16.8 Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants