-
Notifications
You must be signed in to change notification settings - Fork 46
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
Add general notes field to recipes #1082
Comments
Is the field persistent across revisions, or is a new one created each time? I'm also going to assume this is for general note keeping and not actually holding a conversation on the page (a la threaded comments). |
I think this should be part of the revisions, in that it is versioned along with all the other fields. It will require adding a new field to the API, as well as UI for it. And yes, this isn't intended to be used for conversation. We don't need to track authorship or threading or anything like that. The main purpose here is to provide a space for notes that are useful in explaining a recipe. Recently there were some opt-out studies that abused the Study Description field to do this. The problem being that Study Description is user facing data. (#1081 covers this). |
@rehandalal I think this would be a good PR for getting back into Normandy. |
Turns out we already have this field: https://github.com/mozilla/normandy/blob/master/normandy/recipes/models.py#L323 I believe this is a remnant of reversion. It is currently not used in the UI and exposed as a read only field in the API. I don't think there is any value to the historical data in this field so we should probably just use this going forward as the comments field. @mythmon thoughts? |
It also seems we haven't ever used this for anything useful:
(Notably, we also don't paginate the revision endpoint, which we probably should) |
Yes, lets use that field for this. |
Every recipe should have a comments field that recipe editors can save arbitrary notes about the recipe in. This could be related bugs or documents, or explanation of what's going on. This should not be visible to users (public API is fine), related to any particular action, or have any other purpose.
The text was updated successfully, but these errors were encountered: