discourse-custom-header-links/settings.yml

custom_header_links:
  type: objects
  default: []
  schema:
    name: "link"
    identifier: text
    properties:
      text:
        type: string
        required: true
        validations:
          min_length: 1
          max_length: 100
      title:
        type: string
        validations:
          min_length: 1
          max_length: 1000
      url:
        type: string
        required: true
        validations:
          min_length: 1
          max_length: 2048
          url: true
      view:
        type: enum
        choices:
          - vdm
          - vdo
          - vmo
      target:
        type: enum
        choices:
          - blank
          - self
      hide_on_scroll:
        type: enum
        choices:
          - remove
          - keep
        default: keep
      locale:
        type: string

links_position:
  default: right
  type: enum
  choices:
    - right
    - left
DEV: Rename `Custom_header_links` settings to `custom_header_links` (#45) Why this change? Using uppercase in settings name is not part of our convention so renaming it here. 2024-01-25 21:15:41 -05:00			`custom_header_links:`
DEV: Migrate custom header links to new objects setting type (#53) Why this change? Since discourse/discourse@a440e15, we have started to support objects typed theme setting so we are switching this theme component to use it instead as it provides a much better UX for configuring the settings required for the theme component. 2024-04-22 23:50:20 -04:00			`type: objects`
FIX: Ensure that custom header links migration do not fail validation (#55) This commit is a follow up to 73747938bde3c2d3f6f68350c48a320364be1b04 where the migration will fail because the objects created by the migration will end up failing to save because the objects will fail the validation given the new schema. This commit updates the migration to ensure that we do not end up with invalid objects. 2024-04-26 00:57:46 -04:00			`default: []`
DEV: Migrate custom header links to new objects setting type (#53) Why this change? Since discourse/discourse@a440e15, we have started to support objects typed theme setting so we are switching this theme component to use it instead as it provides a much better UX for configuring the settings required for the theme component. 2024-04-22 23:50:20 -04:00			`schema:`
			`name: "link"`
FIX: Ensure that custom header links migration do not fail validation (#55) This commit is a follow up to 73747938bde3c2d3f6f68350c48a320364be1b04 where the migration will fail because the objects created by the migration will end up failing to save because the objects will fail the validation given the new schema. This commit updates the migration to ensure that we do not end up with invalid objects. 2024-04-26 00:57:46 -04:00			`identifier: text`
DEV: Migrate custom header links to new objects setting type (#53) Why this change? Since discourse/discourse@a440e15, we have started to support objects typed theme setting so we are switching this theme component to use it instead as it provides a much better UX for configuring the settings required for the theme component. 2024-04-22 23:50:20 -04:00			`properties:`
			`text:`
			`type: string`
			`required: true`
			`validations:`
			`min_length: 1`
			`max_length: 100`
			`title:`
			`type: string`
			`validations:`
			`min_length: 1`
			`max_length: 1000`
			`url:`
			`type: string`
			`required: true`
			`validations:`
			`min_length: 1`
			`max_length: 2048`
			`url: true`
			`view:`
			`type: enum`
			`choices:`
			`- vdm`
			`- vdo`
			`- vmo`
			`target:`
			`type: enum`
			`choices:`
			`- blank`
			`- self`
			`hide_on_scroll:`
			`type: enum`
			`choices:`
			`- remove`
			`- keep`
			`default: keep`
			`locale:`
			`type: string`
FEATURE: Add setting to show links on the left or right 2019-11-12 15:50:13 -05:00
			`links_position:`
			`default: right`
			`type: enum`
			`choices:`
			`- right`
			`- left`