adam-marshall

Results 9 comments of adam-marshall

Question: why I can't start the spinner?

+1 for timeout

MODULE_INITIALIZER like APP_INITIALIZER

just to add my use case in here... so I have a workflow where a user authenticates, and then once logged in their configuration is requested over HTTP. this configuration...

Unified Control State Change Events (FormControl should also support pristine/touched/untouched/valid events)

I also encountered this. My use case was styling a custom 'inner' control made of multiple inputs when invalid and touched. Calling `form.markAllAsTouched()` on the parent form sets the 'outer'...

Bug (?) - ReactiveForms > FormArray, trackBy index > removeAt & subscriptions

The `this.formArray.controls.findIndex(control => control === myControl)` works for me, but it can be particularly painful for nested groups of controls. E.g. finding the arrayIndex where the array contains a group,...

WARNING in ./node_modules/froala-editor/js/plugins.pkgd.min.js 7:232951-232968 Module not found: Error: Can't resolve 'crypto' in 'C:\Users\Maduranga\Desktop\laravel\Kithu-Raawa\node_modules\froala-editor\js' BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default. This is no longer the case. Verify if you need this module and configure a polyfill for it. If you want to include a polyfill, you need to: - add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }' - install 'crypto-browserify' If you don't want to include a polyfill, you can use an empty module like this: resolve.fallback: { "crypto": false } webpack compiled with 1 warning Notifications are disabled

FYI if I use the individual plugin imports, I don't get this error.

ReactiveForm / FormControl with initial value

This still seems to be an issue. Has anyone attempted to resolve this by using a ControlValueAccessor approach?

ReactiveForm / FormControl with initial value

We stepped through as it seems the `FroalaEditorDirective` is a ControlValueAccessor already so we really wanted to get it working using `[formControl]`. As pointed out in the original post, `[froalaView]`...

formControlName could not be used with component transclusion

I can manage to get `viewProviders: [{ provide: ControlContainer, useExisting: FormGroupDirective }]` working such that `[formGroup]` is on the parent component, and `[formControlName]` is on the child, and all works...

formControlName could not be used with component transclusion

> Any ideas? In case anyone cares, I managed to get rid of the repetition part by using templating in combination with content projection, both together (couldn't use content projection...