choko
choko copied to clipboard
recidive
Choko Framework
Add a "machinename" field and element types for using in name fields and automatically generate machine names for items when adding them. There should be an option for choosing the...
When you navigate out of your application, e.g. clicking on an external link, when you click the browser back button it will return the JSON response for the page instead...
Verify all type definitions, checking for properties, fields and access settings and add missing stuff.
Right now the display name is tied to display mode name, we need to change that, by adding a `displayMode` property to display instances.
Get Choko version from package.json and use it when there's a hardcoded version number. Add this to page state to be consumed by the frontend too.
Currently we replace the entire `content` region which generates a little glitch when switching page content between pages states. There's a `@todo` about it in controllers.js.
Currently our content negotiation is hardcoded for returning the index.html to make the html5mode work in angular, we should improve it and allow extensions to override/extend it in some way.
Allow "list" reference type that would create an aditional endpoint e.g. rest/myType/some-item/myReferenceFieldName, so for e.g. if we have blog posts on path rest/blog/some-blog-post, we could have a list reference field...