Skip to content
This repository was archived by the owner on Apr 3, 2024. It is now read-only.

When using custom categories - it is not possible to create a category with N/A #350

@acastle-optimist

Description

@acastle-optimist

When creating a custom category and setting initial preference to 'N/A' the consent manager displays correctly when launched however once preferences have been chosen and the manager is then relaunched, essential is displayed with Yes No option elements instead of 'N/A'. Using contentManager in Next with current NPM package.

const customCategories = { 'everything': { purpose: 'A new consent category for all integrations', integrations: [ 'Google Analytics', 'Visual Tagger', 'Google Tag Manager', 'Amplitude', 'Webhooks', 'Actions Google Analytic 4', ], }, 'Essential cookies': { purpose: 'Cookies that are needed to operate the website', integrations: [], }, };

const initialPreferences = { 'Essential cookies': 'N/A', };

image

after preferences chosen and the manager is relaunched:

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions