Why am I forced to assign values before linking a new object with another object? I get a 400 error if I link a new object before assigning values to all required properties. Linking at the end works though.1 vote
Imagine something like this:
attribute name : String;
attribute email : String;
attribute telephone : String;
contactInfo : ContactDetails;
Need a log showing activity/errors for my application. I want to see how the app is being used. And in the case of errors, I'd like to have some information on what is wrong and hopefully how to address it.1 vote
For instance: "Relationship reporter failed validation"
I still don't know the reason, so as a user I have no idea of how to remedy it.
It would be great if the entity was also included in the message.0 votes
It should be dead easy to start a new project. There should be a one-step action that allows me to create a project directory with a mdd.properties file and maybe a TextUML source file and a data snapshot file.0 votesAdminRafael Chaves (Admin, Cloudfier) responded
Agreed. See: https://github.com/abstratt/cloudfier/issues/206
UI won't open if I use a # in a property name. Should be able to use user-friendly names in application symbols such as "comment #".0 votes
Currently they are just ignored as actions. The REST endpoint could return the object created.
Concrete example: Issue#reportIssue could return the issue created, so the UI could show it to the user once the creation succeeds.0 votesAdminRafael Chaves (Admin, Cloudfier) responded
Agreed, see: https://github.com/abstratt/kirra-ui/issues/40
- Don't see your idea?