Closed dostuffthatmatters closed 3 years ago
Can you think of a use case where we would need it to be returned? E.g. when you access the survey in the console? If not, it makes sense to me, too, to not return drafts, as it's a route without authentication. So: return drafts on GET /users/{username}/surveys
, don't return on GET /users/{username}/surveys/{survey_name}
?
Yes! That's what I think too.
If we want to render drafts to the authenticated creator we can do that later but for now this is better.
I think in draft mode the API should not respond with the drafted config, since it is not "published".
What do you think?