Project

General

Profile

Actions
Copy link

Task #6029

closed

Feature #6019: Implement "get view" service as a REST endpoint

Implement MN.listViews()

Added by ben leinfelder almost 11 years ago. Updated almost 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
ben leinfelder
Target version:
1.0.0
Start date:
07/08/2013
Due date:
% Done:

0%

Estimated time:

Description

To match the MN.query() paradigm in which supported queryEngine types can be listed on the MN, we should list supported/registered view "engines" (aka qformats or skins).
Would probably start with all the configured skin names as a first pass, maybe throw in "xml" for good measure.

Targeting REST endpoint: 

GET /views

Actions
Copy link
 #1

Updated by ben leinfelder almost 11 years ago

  • Status changed from New to Rejected
  • translation missing: en.field_remaining_hours set to 0.0

Let's revisit this some other time -- not sure how this would be beneficial to clients. UIs would typically not be dynamic so as to just allow user to decide which view to utilize willy-nilly.

Actions
Copy link

Also available in: Atom PDF