Refactor Plausible configuration and update app settings

[johnnyhuy]

PR Type

Enhancement, Configuration changes, Other

---

Description

• Refactored Plausible configuration properties, renaming domain to dataDomain and adding sourceDomain.
• Updated PlausibleAnalytics component to use new configuration properties and modified script source URL.
• Updated test cases to reflect changes in Plausible configuration.
• Updated environment variable names for data and source domains.
• Removed unused .release-it.json configuration file.
• Updated production app configuration to include new Plausible properties.
• Disabled plausible feature in the main app configuration.

---

Changes walkthrough 📝

	Relevant files
Enhancement	config.d.ts Update Plausible configuration properties                                plugins/plausible/config.d.ts Renamed domain property to dataDomain Added new sourceDomain property +6/-1      PlausibleAnalytics.tsx Refactor PlausibleAnalytics component for new configuration plugins/plausible/src/components/PlausibleAnalytics.tsx Updated component to use dataDomain and sourceDomain properties Modified script source URL to use sourceDomain +5/-9
Tests	plugin.test.tsx Update plugin test cases for new configuration                      plugins/plausible/src/plugin.test.tsx Updated test cases to reflect changes in configuration properties +3/-2
Configuration changes	.env.example Update environment variable names                                                .env.example Updated environment variable names for data and source domains +2/-1      app-config.production.yaml Update production app configuration for Plausible                app-config.production.yaml Added enabled, dataDomain, and sourceDomain fields under plausible +3/-1      app-config.yaml Disable Plausible feature in app configuration                      app-config.yaml Disabled plausible feature Removed domain field +1/-2
Other	.release-it.json Remove unused .release-it.json file                                            .release-it.json Deleted unused configuration file +0/-7

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[johnnyhuy]

/describe
--pr_description.publish_labels=false
--pr_description.generate_ai_title=true
--pr_description.final_update_message=true

[johnnyhuy]

/review

[echohello-codium-ai-pr-agent]

PR Review 🔍

(Review updated until commit 4ebd0ae)

⏱️ Estimated effort to review [1-5]	3, because the PR involves multiple configuration changes across different files, including TypeScript and YAML, and also includes logic changes in a React component. Understanding the implications of these changes requires a good grasp of the project's configuration management and the Plausible analytics integration.
🧪 Relevant tests	Yes
⚡ Possible issues	Possible Bug: There is a typo in the property name soureDomain which should be sourceDomain. This could lead to runtime errors or misconfigurations because the property name does not match its usage in the code.
🔒 Security concerns	No

Code feedback:

---

relevant file	plugins/plausible/config.d.ts
suggestion	Correct the typo in the property name from soureDomain to sourceDomain to ensure consistency and avoid potential runtime errors. [important]
relevant line	soureDomain: string;

---

[echohello-codium-ai-pr-agent]

PR Description updated to latest commit (4ebd0ae)

[echohello-codium-ai-pr-agent]

Persistent review updated to latest commit 4ebd0ae

[echohello-codium-ai-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible bug	Correct a typo in the property name to ensure consistency and prevent errors Correct the typo in the property name from soureDomain to sourceDomain to maintain consistency and avoid potential bugs due to misspelling. plugins/plausible/config.d.ts [16] -soureDomain: string; +sourceDomain: string; Suggestion importance[1-10]: 10 Why: Correcting a typo in a property name is crucial to prevent potential bugs and ensure consistency across the codebase.	10
Enhancement	Add error logging for missing configuration to enhance debugging and reliability Add error handling or logging when dataDomain or sourceDomain are not provided, to aid in debugging and ensure the application behaves as expected in error scenarios. plugins/plausible/src/components/PlausibleAnalytics.tsx [11-13] if (!enabled || !dataDomain || !sourceDomain) { + console.error("Plausible Analytics configuration error: Missing required domains."); return null; } Suggestion importance[1-10]: 9 Why: Adding error logging for missing configuration enhances debugging and reliability, which is important for maintaining robust applications.	9
	Enhance test coverage by verifying behavior when configuration domains are missing Update the test to include checks for the absence of dataDomain or sourceDomain to ensure the component behaves correctly under these conditions. plugins/plausible/src/plugin.test.tsx [44] +const { container } = render( - Suggestion importance[1-10]: 8 Why: Enhancing test coverage to verify behavior when configuration domains are missing is beneficial for ensuring the component handles edge cases correctly.	8