Lody Borgers comments

Results 8 comments of


                                            Lody Borgers

Use absolute paths in TsConfigPathsPlugin

I also have this issue. For my test cases I have a separate `tsconfig.test.json` which uses `baseUrl` and `paths` for path resolution within the test cases (using the resolution 'App/*'...

When I use mocks, where do I leave them?

While @MarcLoupias's comment is very solid and generally sound advice, I do create a separate mock file whenever the service that I'm mocking is more generic, like your `api.service.js`. The...

Stencil Component attributes are missing typing info in Angular

@splitinfinities Thank you for the response. If there's something I can help out with, especially with testing then let me know.

@adamdbradley do you know if there's a technical reason for this limitation? If not, does it make sense to offer a way to suppress this warning somehow?

So if I read this correctly, then this would be the proper way to send out a change event: ```tsx @Component({ tag: 'my-input', shadow: true, }) export class MyInput {...

@adamdbradley do you know if there's a technical reason for this limitation? If not, does it make sense to offer a way to suppress this warning somehow?

I just found an example in the output-targets repo: https://github.com/ionic-team/stencil-ds-output-targets/blob/ad7e6605c372e6e98672a26ddf9e99f7343a9fc8/packages/example-project/component-library/src/components/my-input/my-input.tsx In that file the `my-input` component has defined its own `myChange`, `myInput`, `myFocus`, and `myBlur` events instead of using `dispatchEvent()`...

@adamdbradley do you know if there's a technical reason for this limitation? If not, does it make sense to offer a way to suppress this warning somehow?

@MarkChrisLevy Yes, I understand. My question was about which option would be preferred of we have a Stencil component that is just a wrapper with styles around an `input` field:...

@adamdbradley do you know if there's a technical reason for this limitation? If not, does it make sense to offer a way to suppress this warning somehow?

@MarkChrisLevy I think I understand what you mean, and why Stencil prefers it that way. In that case I think a clarification (with maybe some examples) would be a good...

@adamdbradley do you know if there's a technical reason for this limitation? If not, does it make sense to offer a way to suppress this warning somehow?

Yeah I saw when I read through the source code for `@Event`. We are working towards moving the events for our input fields towards `@Event` decorators. Thank you!