[wp-meta] [Making WordPress.org] #3474: Introduce `serve-happy` API endpoint
Making WordPress.org
noreply at wordpress.org
Mon Feb 26 00:13:59 UTC 2018
#3474: Introduce `serve-happy` API endpoint
--------------------------------------+-----------------------
Reporter: flixos90 | Owner: dd32
Type: task | Status: accepted
Priority: normal | Milestone:
Component: API | Resolution:
Keywords: has-patch has-unit-tests |
--------------------------------------+-----------------------
Comment (by flixos90):
After writing code for
https://core.trac.wordpress.org/attachment/ticket/41191/41191.4.diff, I
think it's actually better to continue relying on the individual
parameters, instead of `status`, as for our specific case at this point in
core, we need to look at both things individually (out of date ''and''
insecure). So the `status` property could as well be removed.
The other minor thing that could be improved is: I suggest changing
`receiving_security_updates` to something like `insecure` so that it
aligns with the "negative" connotation of `out_of_date`, for better
consistency. That means if any of the two values is `true`, you have
something to improve. :)
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3474#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list