Activity

1. JeanMeche

   added

   area: forms

   on Feb 18, 2025
2. ngbot

   added this to the needsTriage milestone on Feb 18, 2025
3. JeanMeche commented on Feb 18, 2025

   

   JeanMeche

   on Feb 18, 2025

   Member

   More actions

   This seems to be an issue around the FormRecord.setValue (which is used to infer the type of getRawValue())

   It is currently typed as

     setValue(
       value: {[key: string]: ɵValue<TControl>},
       options?: {
         onlySelf?: boolean;
         emitEvent?: boolean;
       },
     ): void;
   

   When arguably it should be

     setValue(
       value: {[key: string]: ɵRawValue<TControl>},
       options?: {
         onlySelf?: boolean;
         emitEvent?: boolean;
       },
     ): void;
   
4. thePunderWoman

   added a commit that references this issue on Feb 18, 2025

   fix(forms): Fix typing on `FormRecord`. (#59993)

   ...

   This issue will close once commit ec1e4c3 is merged into the 'main' branch.

   ec1e4c3
5. thePunderWoman

   closed this as completedin cf36951on Feb 18, 2025
6. crisbeto

   added a commit that references this issue on Feb 18, 2025

   fix(forms): Fix typing on `FormRecord`. (angular#59993)

   ...

   This issue will close once commit cf36951 is merged into the 'master' branch.

   cf36951
7. angular-automatic-lock-bot commented on Mar 21, 2025

   

   angular-automatic-lock-botBot

   on Mar 21, 2025

   More actions

   This issue has been automatically locked due to inactivity.
   Please file a new issue if you are encountering a similar or related problem.

   Read more about our automatic conversation locking policy.

   _{This action has been performed automatically by a bot.}
8. angular-automatic-lock-bot

   locked and limited conversation to collaborators on Mar 21, 2025