[keycloak-dev] Upgrade Angular?

[Stan Silvert]

On 8/19/2015 2:11 AM, Stian Thorgersen wrote:
> I'm not aware of any reasons we can't upgrade, but we would need to take care and do extra testing of the admin console afterwards.
>
> I'd prefer to upgrade to 1.4.4 early in a Sprint, so if you can upgrade this week, that's fine. Otherwise I'd like to wait to 1.6 release cycle.
I think we should wait until a fresh sprint.

We may need a Sprint that is partially or fully dedicated to the UI.  
It's going to be a big job to go through the UI and replace every bit of 
static text and static message with an angular-translate lookup.   As 
you suggested, it probably makes sense to divide that work up among the 
team members.

When we do that, we should also upgrade Angular.  That way, everyone is 
covering the full UI to make sure that everything is localized and every 
part works properly with Angular 1.4.x.

Sound like a good plan?
>
> ----- Original Message -----
>> From: "Stan Silvert" <ssilvert at redhat.com>
>> To: keycloak-dev at lists.jboss.org
>> Sent: Tuesday, 18 August, 2015 9:59:47 PM
>> Subject: [keycloak-dev] Upgrade Angular?
>>
>> We are using AngularJS 1.2.13.  The latest version is 1.4.4.
>>
>> The reason I ask is because I am a little worried about performance as
>> we begin to use angular-translate.  We are going to end up with a lot of
>> $$watchers, which will eventually make the UI sluggish.
>>
>> There is a solution starting with Angualr 1.3 that lets you specify a
>> one-time-binding using double colons like this {{ ::value }}.
>>
>> Any reason why we can't upgrade?
>>
>> Stan
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>