Properties | PHP properties implementation

A functional approach would be (but probably not clean)

See microsoft/TypeScript#43667 for a canonical answer. This is a design limitation of TypeScript.

As you might be aware: in TypeScript's structural type system, Child is a subtype of Base even though it is not explicitly declared as such. So every value of type Child is also a value of type Base (although not vice-versa). That means Child | Base is equivalent to Base... although the compiler is not always aggressive about reducing the former to the latter. (Compare this to the behavior with something like "foo" | string, which is always immediately reduced to string by the compiler.)

Subtype reduction is often desirable, but there are some places where Child | Base's behavior is observably different from Base's, such as excess property checks, IntelliSense hinting, or the sort of unsound type guarding that happens with the in operator. You haven't shown why it matters to you that you are getting a Base as opposed to a Child | Base, but presumably it's one of these observable differences or something like it.

My advice here is first to think carefully about whether or not you really need this distinction. If so, then you might consider preventing Base from being a subtype of Child, possibly by adding an optional property to it:

You mean to use map instead of forEach.

You can use a type predicate to define a user-defined type guard like this:

Although they 'don't exist', can Format.ps1xml files be created/used in versions of PowerShell greater than 5.1?

• Yes; in fact any third-party code must use them to define custom formatting.

  • That *.ps1xml files are invariably needed for such definitions is unfortunate; GitHub issue #7845 asks for an in-memory, API-based alternative (which for type data already exists, via the Update-TypeData cmdlet).

• It is only the formatting data that ships with PowerShell that is now hardcoded into the PowerShell (Core) executable, presumably for performance reasons.

is there some better practice for suggesting to PowerShell how a certain function should format returned data?

The lack of an API-based way to define formatting data requires the following approach:

• Determine the full name of the .NET type(s) to which the formatting should apply.

  • If it is [pscustomobject] instances that the formatting should apply to, you need to (a) choose a unique (virtual) type name and (b) assign it to the [pscustomobject] instances via PowerShell's ETS (Extended Type System); e.g.:

    • For [pscustomobject] instances created by the Select-Object cmdlet:

Starting with 6.4 RC5 (which is the version you run as of this writing and should provide this in your original post):

The collection of thymeleaf user interface template pages are no longer found in the context root of the web application resources. Instead, they are organized and grouped into logical folders for each feature category. For example, the pages that deal with login or logout functionality can now be found inside login or logout directories. The page names themselves remain unchecked. You should always cross-check the template locations with the CAS WAR Overlay and use the tooling provided by the build to locate or fetch the templates from the CAS web application context.

https://apereo.github.io/cas/development/release_notes/RC5.html#thymeleaf-user-interface-pages

Please read the release notes and adjust your setup.

All templates are listed here: https://apereo.github.io/cas/development/ux/User-Interface-Customization-Views.html#templates

The best I have so far is { person: message.person, tag: 1 }.

Is there shorthand initializer syntax to achieve this?

No, this is still they way to go.

hoping that a property name would magically be inferred from person

You should use constructor injection. And because you already injection Llaveompo you don't need to have @Value for the secret.

Please enable the quarkus-smallrye-jwt TRACE logging to see why the tokens are rejected. And indeed, as you have also found out, https protocol needs to be enabled in the native image, which can be done, as you have shown :-), by adding --enable-url-protocols=https to the native profile's properties in pom.xml.

This PR will ensure adding it manually won't be required.

thanks