HelloWorld
\n```\n\nYou can setup different sanitisaton configurations (profiles) in app config (`app.config.ts`) using the `sanitiseHtml`\nkey.\n\n```ts\nexport default defineAppConfig({\n sanitiseHtml: {\n profiles: {\n profileName: {\n config: {\n allowedTags: [\n 'h1'\n ]\n }\n }\n }\n }\n})\n```\n\nThe profile names can be used as arguments to `v-sanitise-html` to use that profile instead of the default profile.\n\n```vue\n\n\n\n \n\n```\n\nYou can also override the profile used when calling `v-sanitise-html` without arguments by simply setting up a profile\nwith the name `default`.\n\n```ts\nexport default defineAppConfig({\n sanitiseHtml: {\n profiles: {\n // This profile is now used when using `v-sanitise-html` without arguments\n default: {\n config: {\n allowedTags: [\n 'h1'\n ]\n }\n }\n }\n }\n})\n```\n\nProfiles consist of 2 parts: the configuration, which is DOMPurify's configuration but with the keys renamed to\ncamelCase, and the hooks. Please see [DOMPurify documentation](https://github.com/cure53/DOMPurify?tab=readme-ov-file#can-i-configure-dompurify)\nfor more details the configuration. For the hooks configuration object, the keys are the DOMPurify entry point names,\nand the values are either a hook function or an array of hook functions.\n\n```ts\nexport default defineAppConfig({\n sanitiseHtml: {\n profiles: {\n profileName: {\n config: {\n allowedTags: [\n 'h1'\n ],\n ...\n },\n\n hooks: {\n beforeSanitizeAttributes: (currentNode) => {\n // Do something with the node\n },\n\n afterSanitizeAttributes: [\n (currentNode) => {\n // Do something with the node\n },\n\n (currentNode) => {\n // Do another with the node\n }\n ],\n ...\n }\n }\n }\n }\n})\n```\n\n## Contribution\n\nThis repo follows [GitLab Flow](https://about.gitlab.com/topics/version-control/what-is-gitlab-flow/) as a branching\nmodel. All PRs should be made against `development` and not `main`.\n\n