abstratt / kirra-ui Goto Github PK

Receive payment should not be showing below:

but works correctly on the single object view:

Attempting to execute the action does fail due to lack of permissions though.

For the model, see abstratt/cloudfier-sustainable-jersey@63857c7.

For some applications with no queries, a dashboard will show empty. That is bad.

Maybe we should show counts of entities regardless of state, not only for queries.

Successful log in is getting stuck if server returns 204 (cloudfier prototypes).

Do not offer to unlink unmodifiable links (either because are readonly or required).

When an action deletes the current object, go elsewhere. Right now, we try to reload the instance, getting a 404, and show an "Instance not found" error message.

Support for actions on child objects.

The dashboard is hitting queries the user does not have access to, triggering the login dialog.

Workaround was to change the model so all dashboard-worthy queries required no permissions.

Need a proper UI for child objects. Should embed their read-only views or something similar to what was done in the legacy UI.

This would be nice to have.

Add support for adding a child object that is typed by a polymorphic association.

Right now we try to use a type that maybe subclassed and either don't offer the user a chance to choose a type that is more specific, or fail due to the type not being instantiable.

Provide support for pagination.

Expose queries (with or without parameters) in the UI.

Dates are off by a day.

Enumeration literals with multiple words do not show in drop downs.

In this case, this is the result of creating a new cart for the current customer. The URL looks like this:

http://localhost/kirra-angular/?theme=&app-uri=http://localhost/services/api-v2/demo-cloudfier-apps-cesta/#/cesta.Cesta//show

Note the lack of an objectId for the cart.

Disable/hide actions a user does not have permissions for.

For instance, when a shopping car exposes an openOrder action that returns the order opened, show the order.

Case at hand: when starting an order, user is seeing some other existing object.

A workaround would be to direct the user to the dashboard upon login.

A boolean parameter in operation is showing as text. Should be a check box/toggle button.

Provide support for geolocation.

It seems Edge and IE cache Ajax requests, which prevents the UI to reflect changes just performed.

Need to disable caching in all XHR requests we make.

Provide support for user roles.

The inherited properties should show before own properties in UI for child instances.

In this example, 'name' is an inherited property and should show before registeredCode. As a side note, field labels should also be allowed to take more horizontal space if needed.

Same as #12, but for non-aggregation associations.

For queries, dates are being sent as typed by the user in the query parameters (say, 2016/02/13).

1 - static strings should be translatable
2 - support for locale-speciic formats for dates, numbers and currencies

Users should be able to delete objects.

Show enumeration values as user-friendly strings ("In Progress" instead of "InProgress").

Dashboard: split entries in different rows per entity.

Allow signing up.

Global, and integrated with queries.

Brought up by a user.

Implement support for date formatting/validation.

When the list is finally loaded, it should try to match what has been typed so far.

Clicking the app logo should take the user to the main page.

Support toggling bootstrap themes, for instance, using the free Bootswatch themes.

Support locale-sensitive currency/date format. Hmm, we may need a currency type...

Currently, a required parameter in an action can be omitted - we should alert the user instead and refuse to submit the request.

The instance list view is not showing inherited optional relationships. I think this may be by design (to minimize the number of columns shown, but we may need to reconsider). See discussion in #12.

Support a mobile-friendly theme.

Form not showing any fields on creation, or optional fields on editing.

CC: @kenlyle

Allow logging in.

Should compute action enablement lazily, t may be too expensive for servers to compute applicable actions for a list of instances.

This aplpication requires login. Instead of opening the login dialog, it is showing an empty dashboard.

The client should be able to figure out if logging in is required for this application, and if so, show the login dialog..