Ensure we process experiment_fields on save - #9
Merged
Merged
Conversation
Closed
ryanmitchell
marked this pull request as ready for review
February 11, 2026 17:24
|
@ryanmitchell I think I did this correct, but I'm afraid it didn't work. When I created a new experiment and saved, this is what ends up in the .yaml-file: experiment_fields:
fields:
- content
values: nullI do not get any errors in /cp, it says "Saved" and no warnings in the developer console. When I reverted to the 1.0.6 version and saved the Experiment, the yaml-file looks complete again (with the assets prefix as expected) |
Contributor
Author
|
@espenlg would you be able to give me a repository showing the issue? i think I'm misunderstanding the problem. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.