August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-126) Rework the AngularJS scaffolding to support the new REST resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira.... ] Vineet Reynolds closed FORGEPLUGINS-126. ---------------------------------------- Resolution: Done > Rework the AngularJS scaffolding to support the new REST resource representations > --------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-126 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-126 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for handling associations (both n-to-many and n-to-one) since only Ids of the associated fields are required now. > Additional fields that are not a part of the associated resource's representation should not be sent to the server, since it is possible that the server may treat such fields in the incoming JSON representation as not ignorable and respond with a HTTP 400 error. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-126) Rework the AngularJS scaffolding to support the new REST resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira.... ] Vineet Reynolds reopened FORGEPLUGINS-126: ------------------------------------------ > Rework the AngularJS scaffolding to support the new REST resource representations > --------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-126 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-126 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for handling associations (both n-to-many and n-to-one) since only Ids of the associated fields are required now. > Additional fields that are not a part of the associated resource's representation should not be sent to the server, since it is possible that the server may treat such fields in the incoming JSON representation as not ignorable and respond with a HTTP 400 error. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-128) AngularJS scaffold facet is deactivated on exit from the project context

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-128?page=com.atlassian.jira.... ] Vineet Reynolds reopened FORGEPLUGINS-128: ------------------------------------------ > AngularJS scaffold facet is deactivated on exit from the project context > ------------------------------------------------------------------------ > > Key: FORGEPLUGINS-128 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-128 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > After incorporating the fix for FORGEPLUGINS-124, the following behavior is observed. Exiting from the project context either by changing the directory or by restarting Forge, the AngularJS facet installed in the project is lost and the scaffolding needs to be setup once again. > This is due to the project-scoped configuration not being activated before invocation of {{Facet.isInstalled()}}. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-126) Rework the AngularJS scaffolding to support the new REST resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira.... ] Vineet Reynolds closed FORGEPLUGINS-126. ---------------------------------------- Pushed upstream: https://github.com/forge/angularjs-scaffoldx-plugin/commit/14b672ab907c87... > Rework the AngularJS scaffolding to support the new REST resource representations > --------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-126 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-126 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for handling associations (both n-to-many and n-to-one) since only Ids of the associated fields are required now. > Additional fields that are not a part of the associated resource's representation should not be sent to the server, since it is possible that the server may treat such fields in the incoming JSON representation as not ignorable and respond with a HTTP 400 error. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-128) AngularJS scaffold facet is deactivated on exit from the project context

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-128?page=com.atlassian.jira.... ] Vineet Reynolds closed FORGEPLUGINS-128. ---------------------------------------- Pushed upstream: https://github.com/forge/angularjs-scaffoldx-plugin/commit/687a46ea932f1b... > AngularJS scaffold facet is deactivated on exit from the project context > ------------------------------------------------------------------------ > > Key: FORGEPLUGINS-128 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-128 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > After incorporating the fix for FORGEPLUGINS-124, the following behavior is observed. Exiting from the project context either by changing the directory or by restarting Forge, the AngularJS facet installed in the project is lost and the scaffolding needs to be setup once again. > This is due to the project-scoped configuration not being activated before invocation of {{Facet.isInstalled()}}. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-134) Upgrade the Forge API version used to 1.4.0

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-134: -------------------------------------------- Summary: Upgrade the Forge API version used to 1.4.0 Key: FORGEPLUGINS-134 URL: https://issues.jboss.org/browse/FORGEPLUGINS-134 Project: Forge Plugins Issue Type: Task Components: AngularJS Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds We now depend on the ConfigurationFactory API introduced in Forge 1.4.0 as a result of FORGEPLUGINS-128. Therefore, this is the minimum version of Forge that we support. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1129) Support interactive merging of changes performed on existing files

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1129?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1129: ------------------------------------------- hey max, you've mentioned jmerge before, but does that work with the eclipse (accept changes) merge editor? > Support interactive merging of changes performed on existing files > ------------------------------------------------------------------ > > Key: FORGE-1129 > URL: https://issues.jboss.org/browse/FORGE-1129 > Project: Forge > Issue Type: Feature Request > Components: UI - API, UI - Eclipse, UI - IntelliJ IDEA, UI - Shell > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Currently, in Forge 1, we merely prompt the users to overwrite the existing file if located. Either the existing file is lost or the changes made by Forge are not saved. No attempt is made to retain the existing file with changes performed by the user, while merging in changes performed by Forge. > Forge should support interactive diffing and merging of the changes made on the existing file. Integration with existing diff tools in various IDEs and shells would be a plus. > This should ideally be exposed as a service for other addons. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1132) Generated source code should be marked with the javax.annotation.Generated annotation

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1132: -------------------------------------- Summary: Generated source code should be marked with the javax.annotation.Generated annotation Key: FORGE-1132 URL: https://issues.jboss.org/browse/FORGE-1132 Project: Forge Issue Type: Feature Request Affects Versions: 1.4.0.Final Reporter: Vineet Reynolds This would be beneficial in denoting classes or methods that may be regenerated by Forge, thus causing any user-inflicted changes to be lost on subsequent regeneration. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1129) Support interactive merging of changes performed on existing files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1129?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on FORGE-1129: -------------------------------------------- look at jmerge for java code merging. > Support interactive merging of changes performed on existing files > ------------------------------------------------------------------ > > Key: FORGE-1129 > URL: https://issues.jboss.org/browse/FORGE-1129 > Project: Forge > Issue Type: Feature Request > Components: UI - API, UI - Eclipse, UI - IntelliJ IDEA, UI - Shell > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Currently, in Forge 1, we merely prompt the users to overwrite the existing file if located. Either the existing file is lost or the changes made by Forge are not saved. No attempt is made to retain the existing file with changes performed by the user, while merging in changes performed by Forge. > Forge should support interactive diffing and merging of the changes made on the existing file. Integration with existing diff tools in various IDEs and shells would be a plus. > This should ideally be exposed as a service for other addons. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-893) UIInput<?> should support setValidator(UIIInputValidator) getValidator() for input-level-validation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-893?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-893. --------------------------------- Fix Version/s: 2.0.0.Alpha11 (was: 2.x Future) Resolution: Done Implemented. > UIInput<?> should support setValidator(UIIInputValidator) getValidator() for input-level-validation > --------------------------------------------------------------------------------------------------- > > Key: FORGE-893 > URL: https://issues.jboss.org/browse/FORGE-893 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse, UI - IntelliJ IDEA, UI - Shell > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha11 > > > Currently Forge 2 UI API supports command-level validation, but we don't support field-level validation, which would be useful for dev simplification/ease of use. > This may or may not be able to live on the base InputComponent interface, but more likely it will need to be customized for each of UISelectOne, UISelectMany, UIInput, and UIInputMany types. > {code} > public interface InputComponent<IMPLTYPE, VALUETYPE> extends Faceted<HintsFacet> > { > Validator<VALUETYPE> getValidator(); > IMPLTYPE setValidator(Validator<VALUETYPE>); > } > {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

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013