sceee

Results 52 comments of sceee
trafficstars

v4.0.0-beta3: ../primevue/themes/index.d.ts' is not a module when writing and building the app.

Hi @mertsincan @44m0n I think this is just the same issue as #5521 and #5615 . They have been added to the (now closed) 4.0.0-beta.3 milestone but are not closed...

v4.0.0-beta3: ../primevue/themes/index.d.ts' is not a module when writing and building the app.

Thanks @mertsincan , for now I just ignored this error using ```typescript // @ts-expect-error Remove once types are fixed import { definePreset } from 'primevue/themes' ``` but that's obviously not...

Password: Passthrough and IconField not working properly

Side note for v4.0.0-rc.3: The passthrough to access the input of a `Password` needs to be this: `pt:pc-input:root:class="someclass"`. Reason: The `pc-input` is the key for the "input" part of the...

Theming v4: Unable to use CSS layers with tailwind css as primevue injects a declaration of its own layer at the top of the HTML head breaking the `@layer` orders

> Could you maybe add your own stylesheet which just defines the layer order and load it in the main.js? Afaik it will be inserted before any primevue css, so...

Theming v4: Unable to use CSS layers with tailwind css as primevue injects a declaration of its own layer at the top of the HTML head breaking the `@layer` orders

@m-meier oh, nice, thank you very much, this seems to work 👏 I actually found some hints that the name might be configurable, but it was not reflected in the...

Theming v4: Unable to use CSS layers with tailwind css as primevue injects a declaration of its own layer at the top of the HTML head breaking the `@layer` orders

This is now reflected in the docs since v4.0.0-rc1: https://primevue.org/theming/styled/#options ```typescript options: { cssLayer: { name: 'primevue', order: 'tailwind-base, primevue, tailwind-utilities' } } ```

Typescript error with V2 `wrap`: Type '{ data: WhatEverType; }' is missing the following properties from type 'CallableRequest<any>': rawRequest, acceptsStreaming

Hi @CorieW , No, I used `wrap` as described here in the samples: https://github.com/firebase/functions-samples/blob/0dcd3371ab553c4e44590e7e63c9f57f6f1af6f3/Node/test-functions-jest-ts/functions/src/__test__/index.test.ts#L24-L39 This sample is referenced on the Readme of this repo: https://github.com/firebase/firebase-functions-test/blob/53f3e3e733e824835123f54bed75fde683d2c42e/README.md#examples If these samples are outdated...

Typescript error with V2 `wrap`: Type '{ data: WhatEverType; }' is missing the following properties from type 'CallableRequest<any>': rawRequest, acceptsStreaming

Thanks @sbuys for your sample. Of course, you can "make Typescript happy" using something like your mentioned `rawRequest: {} as unknown as CallableRequest['rawRequest'],` but that's definitely not a good way...

Typescript error with V2 `wrap`: Type '{ data: WhatEverType; }' is missing the following properties from type 'CallableRequest<any>': rawRequest, acceptsStreaming

@CorieW just as reminder as I feel something is wrong with the "Needs author feedback" label: I don't know why this issue still has this label as I've given feedback...

Does not work with "parameterized config"

@wneild 's solution seems to actually be a pretty good workaround until `firebase-functions-test` support a similar function as `mockConfig()` for parametrized config. If someone else is looking for this, I...