Context Navigation

← Previous Ticket
Next Ticket →

#18423 closed enhancement (wontfix)

Make internal linking's River + Query constructors public

Reported by:	mitchoyoshitaka	Owned by:	koopersmith
Priority:	normal	Milestone:
Component:	Editor	Version:	3.2
Severity:	normal	Keywords:	has-patch
Cc:		Focuses:	javascript

Description

...and restructure them so that they're slightly more configurable, i.e. making the AJAX endpoint URL and result rendering overrideable.

Attachments (1)

18423.diff (13.7 KB ) - added by mitchoyoshitaka 15 years ago.: 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.

Download all attachments as: .zip

Change History (5)

@mitchoyoshitaka
15 years ago

Attachment 18423.diff added

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.

#1 @mitchoyoshitaka
15 years ago

Owner set to koopersmith
Status new → reviewing

#2 @koopersmith
15 years ago

Milestone Awaiting Review → Future Release
Version → 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?

#3 @jeremyfelt
12 years ago

Focuses javascript added

#4 @wonderboymusic
11 years ago

Milestone Future Release
Resolution → wontfix
Status reviewing → closed

This is a relic from 4 years ago. Mitcho, if your passion is still ignited here, please reopen.

Note: See TracTickets for help on using tickets.

Download in other formats:

Make WordPress Core