[wp-trac] [WordPress Trac] #26673: Enhance wp_parse_args() by adding filters before/after the array_merge()
WordPress Trac
noreply at wordpress.org
Mon Feb 3 01:48:06 UTC 2014
#26673: Enhance wp_parse_args() by adding filters before/after the array_merge()
-----------------------------------+------------------------------
Reporter: johnjamesjacoby | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version:
Severity: normal | Resolution:
Keywords: has-patch 2nd-opinion | Focuses:
-----------------------------------+------------------------------
Comment (by nacin):
Replying to [comment:16 mordauk]:
> Stop using wp_parse_args() throughout core? I like wp_parse_args() for
how it allows flexible input formats. Is there a disadvantage to that I'm
not seeing?
I'm not saying it should be removed. I'd like to stop blindly adding it in
situations where we expect and only want an array. That's probably not
going to happen, but I'd like to continue to treat it like a low-level
utility function not unlike array_merge().
--
Ticket URL: <https://core.trac.wordpress.org/ticket/26673#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list