Entity bundle, field name, CSS class should be less implementation specific

Created on 4 October 2023, about 1 year ago

Updated 19 September 2024, 2 months ago

Problem/Motivation

This module depends on specific conditions for its operation:

It is implemented to add a pseudofield to the content type "resource" only.
It depends on the placement of a block with a specific ID, "sectormultipagepaginationblock".
The JS references the selector .prose from Sector Radix Starter

When I used the module in its default state to place the "Sector Multipage Pagination block", the resulting block ID was "THEMENAME_sectormultipagepaginationblock" not "sectormultipagepaginationblock".

Steps to reproduce

Various, just keeping notes for now!

Proposed resolution

Move this to configuration?

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Needs review

Version

1.0

Component

Code

Created by

🇳🇿New Zealand xurizaemon Ōtepoti, Aotearoa 🏝

Live updates comments and jobs are added and updated live.

Merge Requests

!6Entity bundle, field name, CSS class should be less implementation specific
Open
🇳🇿New Zealand xurizaemon
updated 2 months ago

Comments & Activities

Issue created by @xurizaemon
Comment about 1 year ago →
🇳🇿New Zealand xurizaemon Ōtepoti, Aotearoa 🏝
Comment about 1 year ago →
🇳🇿New Zealand xurizaemon Ōtepoti, Aotearoa 🏝
Merge request !6Issue #3391489: Replace `.prose` selector, bind only once → (Open) created by xurizaemon
Comment about 1 year ago →
🇳🇿New Zealand xurizaemon Ōtepoti, Aotearoa 🏝
Re-titling because "fixed" can mean "hardcoded" or "solved" and I didn't mean the latter :)
First commit to issue fork.
Status changed to Needs review 2 months ago10:17pm 19 September 2024
Comment 2 months ago →
🇳🇿New Zealand ericgsmith

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024