typex | Typography web export plugin | Style Language library

Okay maybe I should have played around a bit more before writing up a question :)

This works:

This object is basically a string-to-object dictionary/hashmap with an extra name property. Fixed properties are defined in properties, and the dictionary part can be defined using either patternProperties (in OpenAPI 3.1) or additionalProperties (in OpenAPI 3.0 and 2.0).

In OAS 3.1 your object can be defined as follows. Since the optional property names all follow the typeX format, the schema uses patternProperties to define the regex for the property names.

TypeScript isn't intelligent enough to prove that x in the second if is indeed a string. Since prints only accepts a string and it cannot prove that x is a string, it gives an error.

The first case, where the type check happens inside the if conditional itself, works because TypeScript has a special case for understanding that kind of type check. However, the understanding that certain values in a certain variable could indicate the type of some other variable is more than it can handle. Yes, in this specific example, it looks like it should be trivial to figure it out, but it would very quickly become extremely difficult or even outright impossible for it to function in the general case.

If you absolutely want the second case to work, despite the type check being separate from the if, you need to provide TypeScript with extra information by explicitly casting the value. For instance, using prints(x as string) means "I guarantee that is is always a string. If it's not, it's my fault when the program explodes." This type of cast is a signal to TypeScript that the developer knows something that it doesn't understand and blindly trusts it.

One solution might be creating a ref for each content-block-ui-frame in the block-editor, and passing the ref to the right content-block-ui-frame as a prop. Is this the approach you meant when you mentioned you already tried it with refs?

EDIT: I was able to create a minimal example where passing the ContentBlock ref as a prop to the ContentblockUiFrame works as expected. The ContentBlockUIFrame components are able to use the methods of ContentBlock.

Check my example here

The non-template version is taking std::function as parameter, and you're passing lambdas, which requires user-defined conversion. The template version is exact match and wins in overload resolution.

You can impose restriction on the template parameter to make it unusable when object being passed could convert to FuncI.

Thanks for both the answers. I used it as below and it worked:

Yes, take a look into generic functions in typescript https://www.typescriptlang.org/docs/handbook/generics.html

Here is what I would do, hope it helps.

1. Is there a way to access to the last 'div' within 'rootDiv', check its class and based on it click any of the buttons?

It is possible to access the last 'div' within 'rootDiv': cy.get('.rootDiv div').last(). However, checking the class and then performing actions based on the value of the class is a bad idea, as it is conditional testing and Cypress was not really made for it. Nevertheless, if you really need this attitude (no other, better ways), I think it is doable.

1. Is there a way to get the 'text' written on the buttons of the last 'div'?

Yes, it is possible to get 'text' of last div. cy.get('.rootDiv div').last().invoke('text').then((textOnTheButton) => {console.log(textOnTheButton})

3.Is there a way to have a list of elements (buttons in this case) and iterate through them?

To get all of the buttons all you need is cy.get(button). If you want to iterate through all of them using index, you may use for loop and eq(), however it may not be the best/most efficient solution for all cases.