[JBoss JIRA] (FORGE-1346) Introduce wildcards to the CLI
by Ståle Pedersen (JIRA)
[ https://issues.jboss.org/browse/FORGE-1346?page=com.atlassian.jira.plugin... ]
Ståle Pedersen commented on FORGE-1346:
---------------------------------------
well, atm this wont be possible in æsh since the completor never remove any text. it can only add. - ive planned to change this in an upcoming version, but i do not know when.
imo i think a feature like this would create more confusion than it would be helpful. i just cant imagine an intuitive way of selecting which command to select. - if you're not thinking of similar to what zsh have?
> Introduce wildcards to the CLI
> ------------------------------
>
> Key: FORGE-1346
> URL: https://issues.jboss.org/browse/FORGE-1346
> Project: Forge
> Issue Type: Enhancement
> Components: UI - Shell
> Affects Versions: 2.x Future
> Reporter: Antonio Goncalves
>
> At the moment you start typing a command, you hit TAB, and you get all the possible hints :
> {code}
> > jpa- TAB
> jpa-new-entity jpa-new-field
> {code}
> If wildcards are introduced, you could then do :
> {code}
> > *scaffold* TAB
> jpa-scaffold-from-db rest-scaffold-from-jpa rest-scaffold-from-ejb
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (FORGE-1346) Introduce wildcards to the CLI
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1346?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1346:
-------------------------------------------
I like this idea. I wonder [~stalep], is there any reason this could not be done that you can think of?
> Introduce wildcards to the CLI
> ------------------------------
>
> Key: FORGE-1346
> URL: https://issues.jboss.org/browse/FORGE-1346
> Project: Forge
> Issue Type: Enhancement
> Components: UI - Shell
> Affects Versions: 2.x Future
> Reporter: Antonio Goncalves
>
> At the moment you start typing a command, you hit TAB, and you get all the possible hints :
> {code}
> > jpa- TAB
> jpa-new-entity jpa-new-field
> {code}
> If wildcards are introduced, you could then do :
> {code}
> > *scaffold* TAB
> jpa-scaffold-from-db rest-scaffold-from-jpa rest-scaffold-from-ejb
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (FORGEPLUGINS-159) Support Temporal fields of type date and time in the AngularJS scaffolding
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-159?page=com.atlassian.jira.... ]
Vineet Reynolds updated FORGEPLUGINS-159:
-----------------------------------------
Description:
The generated AngularJS scaffold treats datetime fields as text fields. It would be preferable to the HTML5 input['datetime'] support, but given that most browsers do not support it yet, we should attempt to support it via Modernizr based detection and a fallback to an input validation driven widget.
was:
The generated AngularJS scaffold treats datetime fields as text fields. It would be preferable to the HTML5 input['datetime'] support, but given that most browsers do not support it yet, we should attempt to support it via Modernizr based detection and polyfills.
This: https://github.com/jonstipe/datetime-polyfill looks like a polyfill that we could consider, but we would need to write an AngularJS directive.
The same applies to this Bootstrap based datetime picker: http://www.malot.fr/bootstrap-datetimepicker/index.php
> Support Temporal fields of type date and time in the AngularJS scaffolding
> --------------------------------------------------------------------------
>
> Key: FORGEPLUGINS-159
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-159
> Project: Forge Plugins
> Issue Type: Feature Request
> Components: AngularJS Scaffold
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
>
> The generated AngularJS scaffold treats datetime fields as text fields. It would be preferable to the HTML5 input['datetime'] support, but given that most browsers do not support it yet, we should attempt to support it via Modernizr based detection and a fallback to an input validation driven widget.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (FORGE-1361) Control REST resource generation to allow entities to be sent in response to POST request
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1361:
--------------------------------------
Summary: Control REST resource generation to allow entities to be sent in response to POST request
Key: FORGE-1361
URL: https://issues.jboss.org/browse/FORGE-1361
Project: Forge
Issue Type: Feature Request
Components: Blessed Plugins
Affects Versions: 2.0.0.Beta3, 1.4.3.Final
Reporter: Vineet Reynolds
The generated REST resources always issue a HTTP 201 Response with a Location header in response to a HTTP POST. Some clients expect the response to contain an entity representation of the newly created resource. Therefore, we should allow users to control whether they want the entity to feature in the response.
This would require:
* the method be annotated with @Produces with the mediatype being the chosen resource representation.
* the entity() method be invoked to populate the entity in the response.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (FORGE-1360) Review Property and Field Access support for JPA and related specs
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1360:
--------------------------------------
Summary: Review Property and Field Access support for JPA and related specs
Key: FORGE-1360
URL: https://issues.jboss.org/browse/FORGE-1360
Project: Forge
Issue Type: Task
Components: Blessed Plugins
Affects Versions: 2.0.0.Beta3
Reporter: Vineet Reynolds
Annotations should be written to the fielld or the getter, based on whether property or field access is used in JPA entities. Likewise, the presence of the annotation should also be flagged based on property vs field access used for the entity.
Note that there are different rules for JPA 1.0 and 2/0 entities. Different rules may also exist for other addons that support other specifications/JSRs involving beans.
This task is to conduct a review of the behavior of Forge addons for scenarios involving property vs field access. Raise additional feature requests or bugs as necessary.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months