grok

REST skins should work like regular skins

Bug #305136 reported by Martijn Faassen
2
Affects Status Importance Assigned to Milestone
grok
Fix Released
High
Jan Wijbrand Kolman
grok 1.0
1.0
Fix Released
High
Jan Wijbrand Kolman
grok 1.0

Bug Description

We use a layer/skin mechanism for Grok's REST support. We changed the regular layer/skin mechanism to a simpler approach recently, but the REST support hasn't been updated. This still has to be done.

todd (todd-infrae)
Changed in grok:
assignee: nobody → janwijbrand
milestone: none → 1.0
Revision history for this message
Jan Wijbrand Kolman (janwijbrand) wrote :

Agreed. I'm working on this.

Changed in grok:
importance: Undecided → High
status: New → In Progress
Revision history for this message
Jan Wijbrand Kolman (janwijbrand) wrote :

Fix checked in.

One remark: I would've liked to name the directive to declare a REST skin "grok.rest()", but this is not possible
since there's already a module named rest.py in the grok package. I chose "grok.restskin()" as an alternative.

If we would really like to have it called "grok.rest()" then I'd propose to rename the rest.py module into something like, maybe, _rest.py

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.