3 deleted 246 characters in body
source | link

AFAIK, you don’t need DCPs to be able to query for Component metadata.

For example, the Latest News widget on the DXA Example Site Home Page queries embedded Component Presentations.

Regarding DXA Resolver not detecting Component Links in RTF: I don’t think that is deliberate. Can you create a GitHub issue for it? I will try to squeeze a fix in DXA 2.2 (even though scope for 2.2 is pretty much full already).

UPDATE

In general, the DXA Resolver is intended to deal with dynamic expansion. That is: linked Components based on a Schema associated with the “Generate Data Presentation” DCT will not get statically expanded on CM-side, but published as separate DCP and dynamically expanded on CD-side. The DXA Resolver ensures that those so-called Data Presentations are resolved/published.

However, Component Links in a RTF are (currently) always statically expanded, regardless of whether their Schema is associated with the “Generate Data Presentation” DCT or not.

That explains why the DXA Resolver doesn’t have to resolve Component Links in a RTF (since these are never dynamically expanded).

You could argue that it should be possible to use dynamic expansion for Component Links in an RTF too, though.

AFAIK, you don’t need DCPs to be able to query for Component metadata.

For example, the Latest News widget on the DXA Example Site Home Page queries embedded Component Presentations.

Regarding DXA Resolver not detecting Component Links in RTF: I don’t think that is deliberate. Can you create a GitHub issue for it? I will try to squeeze a fix in DXA 2.2 (even though scope for 2.2 is pretty much full already).

UPDATE

In general, the DXA Resolver is intended to deal with dynamic expansion. That is: linked Components based on a Schema associated with the “Generate Data Presentation” DCT will not get statically expanded on CM-side, but published as separate DCP and dynamically expanded on CD-side. The DXA Resolver ensures that those so-called Data Presentations are resolved/published.

However, Component Links in a RTF are (currently) always statically expanded, regardless of whether their Schema is associated with the “Generate Data Presentation” DCT or not.

That explains why the DXA Resolver doesn’t have to resolve Component Links in a RTF (since these are never dynamically expanded).

You could argue that it should be possible to use dynamic expansion for Component Links in an RTF too, though.

AFAIK, you don’t need DCPs to be able to query for Component metadata.

For example, the Latest News widget on the DXA Example Site Home Page queries embedded Component Presentations.

In general, the DXA Resolver is intended to deal with dynamic expansion. That is: linked Components based on a Schema associated with the “Generate Data Presentation” DCT will not get statically expanded on CM-side, but published as separate DCP and dynamically expanded on CD-side. The DXA Resolver ensures that those so-called Data Presentations are resolved/published.

However, Component Links in a RTF are (currently) always statically expanded, regardless of whether their Schema is associated with the “Generate Data Presentation” DCT or not.

That explains why the DXA Resolver doesn’t have to resolve Component Links in a RTF (since these are never dynamically expanded).

You could argue that it should be possible to use dynamic expansion for Component Links in an RTF too, though.

2 added 822 characters in body
source | link

AFAIK, you don’t need DCPs to be able to query for Component metadata.

For example, the Latest News widget on the DXA Example Site Home Page queries embedded Component Presentations.

Regarding DXA Resolver not detecting Component Links in RTF: I don’t think that is deliberate. Can you create a GitHub issue for it? I will try to squeeze a fix in DXA 2.2 (even though scope for 2.2 is pretty much full already).

UPDATE

In general, the DXA Resolver is intended to deal with dynamic expansion. That is: linked Components based on a Schema associated with the “Generate Data Presentation” DCT will not get statically expanded on CM-side, but published as separate DCP and dynamically expanded on CD-side. The DXA Resolver ensures that those so-called Data Presentations are resolved/published.

However, Component Links in a RTF are (currently) always statically expanded, regardless of whether their Schema is associated with the “Generate Data Presentation” DCT or not.

That explains why the DXA Resolver doesn’t have to resolve Component Links in a RTF (since these are never dynamically expanded).

You could argue that it should be possible to use dynamic expansion for Component Links in an RTF too, though.

AFAIK, you don’t need DCPs to be able to query for Component metadata.

For example, the Latest News widget on the DXA Example Site Home Page queries embedded Component Presentations.

Regarding DXA Resolver not detecting Component Links in RTF: I don’t think that is deliberate. Can you create a GitHub issue for it? I will try to squeeze a fix in DXA 2.2 (even though scope for 2.2 is pretty much full already).

AFAIK, you don’t need DCPs to be able to query for Component metadata.

For example, the Latest News widget on the DXA Example Site Home Page queries embedded Component Presentations.

Regarding DXA Resolver not detecting Component Links in RTF: I don’t think that is deliberate. Can you create a GitHub issue for it? I will try to squeeze a fix in DXA 2.2 (even though scope for 2.2 is pretty much full already).

UPDATE

In general, the DXA Resolver is intended to deal with dynamic expansion. That is: linked Components based on a Schema associated with the “Generate Data Presentation” DCT will not get statically expanded on CM-side, but published as separate DCP and dynamically expanded on CD-side. The DXA Resolver ensures that those so-called Data Presentations are resolved/published.

However, Component Links in a RTF are (currently) always statically expanded, regardless of whether their Schema is associated with the “Generate Data Presentation” DCT or not.

That explains why the DXA Resolver doesn’t have to resolve Component Links in a RTF (since these are never dynamically expanded).

You could argue that it should be possible to use dynamic expansion for Component Links in an RTF too, though.

1
source | link

AFAIK, you don’t need DCPs to be able to query for Component metadata.

For example, the Latest News widget on the DXA Example Site Home Page queries embedded Component Presentations.

Regarding DXA Resolver not detecting Component Links in RTF: I don’t think that is deliberate. Can you create a GitHub issue for it? I will try to squeeze a fix in DXA 2.2 (even though scope for 2.2 is pretty much full already).