Problem/Motivation

Forum and User modules provide optional RDF config. This needs to be moved to RDF module in preparation for removing RDF from core.

Steps to reproduce

Proposed resolution

See #3243121: Remove RDF module from the Standard profile for how this was done with Standard profile.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#2 3303435-2.patch1.96 KBlongwave
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

longwave created an issue. See original summary.

longwave’s picture

longwave
he/him
Primary language English
Location UK
CreditAttribution: longwave at Full Fat Things commented
Status: Active » Needs review
FileSize
3303435-2.patch1.96 KB

Following the pattern used in the Standard conversion I think this is right?

Spokje’s picture

Spokje
Primary language Dutch
CreditAttribution: Spokje as a volunteer commented
Status: Needs review » Reviewed & tested by the community

Not the enforced relationship expert (well... I am, but that gets us wayyyyy of track..) but it _is_ the same procedure we used in #3243121: Remove RDF module from the Standard profile and TestBot likes it.

I'm going with an RTBC because of the above.

  • catch committed ecf2fe3 on 10.0.x 
    Issue #3303435 by longwave, Spokje: Move RDF-related optional config to...
  • catch committed 6a539e1 on 10.1.x
    Issue #3303435 by longwave, Spokje: Move RDF-related optional config to...
  • catch committed bd489b6 on 9.5.x
    Issue #3303435 by longwave, Spokje: Move RDF-related optional config to...
catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch at Third and Grove commented
Status: Reviewed & tested by the community » Fixed 
+++ b/core/modules/rdf/config/optional/rdf.mapping.user.user.yml
@@ -3,6 +3,9 @@ status: true
     - user
+  enforced:
+    module:
+      - user

Only thing I would say is I think this is a no-op because user module is required, but also don't think it matters.

Committed/pushed to 10.1.x, cherry-picked to 10.0.x and 9.5.x, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.