Opened 13 years ago
Closed 9 years ago
#18423 closed enhancement (wontfix)
Make internal linking's River + Query constructors public
Reported by: | mitchoyoshitaka | Owned by: | koopersmith |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.2 |
Component: | Editor | Keywords: | has-patch |
Focuses: | javascript | Cc: |
Description
...and restructure them so that they're slightly more configurable, i.e. making the AJAX endpoint URL and result rendering overrideable.
Attachments (1)
Change History (5)
#2
@
13 years ago
- Milestone changed from Awaiting Review to Future Release
- Version set to 3.2
I like this idea, but would prefer to iterate and tighten the code up before making it publicly available. I'd also like to wait until we properly establish a JS namespace.
Mitcho, can you elaborate on your use cases for the exposed Query and River classes?
Note: See
TracTickets for help on using
tickets.
Patch v1, refactored so they're in wp.lookup.Query and wp.lookup.River. Also introduces wp.utils, but this should probably be moved out into a separate file in the near future.