rtens / domin Goto Github PK

Required HTML field should show warning if empty on submit

Support number ranges with slider controls

Hide the form and buttons if the action was executed and the results are shown.

At the moment, you have to use domin types to change the controls. There should be a way to configure actions. For example by mapping the parameters both ways.

Actions should be put into collapsed groups on the index page.

At the moment, URLs are serialized manually at a couple of places without support for array parameters. Instead, there should be a URL builder like on curir.

Add an option in the interactive mode to write the output to a file instead of printing it

$ php foo.php ! --out my_file.txt

Output written to [my_file.txt]

Make it possible to provide a description for Actions and Fields for more information.

Rename AccessPolicy to AccessRestriction. Rename methods accordingly.

Should use FOO_*

Exceptions during action execution should be logged besides or instead showing them to the user.

The default logger implementation could print the error to stderr but a monolog implementation should be available.

Make sure that acquiring access is working.

A new Field that allows the input to either be a string or, if prefixed by '@', the input is read from a file.

They shouldn't be per-session (ie cookie) but instead per-window, meaning that it needs to be stored in the page itself. Also, it shouldn't reset when the user visits the action list.

A required list should show a warning if empty on submit

At the moment, domin is highly coupled with curir as a delivery system. Instead, it should be independent of such system and adapters should allow to use almost any and exchange them easily.

Some fields should be disabled if pre-filled. For example IDs when updating entities.

To protect against cross-site request forging, requests should be verified using synchronized tokens. This could also be used in links to enable execution if modifying actions through GET requests.

If a value contains double quotes ("), they need to be escaped when the field is rendered.

Instead of showing the action index, it should be possible to configure domin to execute a certain action by default.

If a File field is required but a file is preserved, it should not be required any more

Currently it doesn't matter if an action is executed with GET or POST. The idea would be to mark actions as "modifying" and only allow non-modifying actions to be exectued with GET. If a modifying action is accessed with GET, the form is displayed but the action not executed, even if no fields are missing.

The form could then even contain an "execution token" that verifies the request.

A simple module that would decide for each execution of an action if the execution is permitted. There should also be a way to define how the user can acquire the permission. For example by providing a URL to be redirected to.

The access control should have no notion of "logged-in", only of "permission denied/granted"

• Enlarge panel title (~24pt)
• Hide "Execute" button if no form is shown

List of input elements can't be selected and edited in Firefox

The action list itself should be an action that is by default registered under a specific identifier like "index" which is set as default action. It should be able to change the default action as well as set a new action with the "index" identifier.

The action returns an ActionList object that has its own renderer.

The routing will have to be changed for each web adapter.

There should be a way to execute action through an API. Input and output is structured data which can be represented in any way (JSON, XML, ...). The application requires its own set of fields and renderers and should also generate documentation (which could be acessed with the OPTIONS method)

Make app have a project name which appears in menu and page titles

In the interactive CLI, put a space between parameter and value and a new line before the output.

htmlentities screws them up

Hello @rtens,

is this project alive? To me it seems to be quite useful.

BR,
Mariyo

Don't print the keys of an array if they're a range starting with zero.

The options of each chart are currently stored in the ChartRenderer but instead it should be part of the Chart itself so it can be overridden without creating a new renderer.

It should be possible to use a certain field for a property, regardless of it's actual type. Converting will be necessary and probably has to be done by hand.

For example "string" could yield a StringField, a TextField or an HtmlField.

Instead of having the form template hard-coded, it should be rendered by a replaceable object, like a form renderer. ObjectField actually already does most of what's needed.