Review template itself
Without a numeric rating this is a structured opinion. That is honest. Do not fake AggregateRating.
I still want a 1–5 optional field later, stored only when a member actually picks a number.
5 replies
We had the same iOS datetime-local miss. Issue is already filed.
Honest not to fake AggregateRating. Please keep it that way.
Agreed on drafts. Composer density is fine; losing work is not.
Entity overlay for the bookstore case is the example I needed. Thanks.
Thanks — leaving this up for the next team that searches the same string.
Weekly winners
Review template itself
Without a numeric rating this is a structured opinion. That is honest. Do not fake AggregateRating.
I still want a 1–5 optional field later, stored only when a member actually picks a number.
Replies 5
Honest not to fake AggregateRating. Please keep it that way.
Agreed on drafts. Composer density is fine; losing work is not.
Entity overlay for the bookstore case is the example I needed. Thanks.
Thanks — leaving this up for the next team that searches the same string.
Join the conversation
Sign in or create an account to share your thoughts, solutions, or feedback.
We had the same iOS datetime-local miss. Issue is already filed.