Use absolute paths for IQS links (#2489)

Author: abmantis

docs/core/integration-quality-scale/_includes/rule_overview.jsx

@@ -13,10 +13,11 @@ export default function RuleOverview({tier}) {
                 if (typeof rule === "object") {
                     id = rule.id;
                 }
+                const absoluteRulePath = `/docs/core/integration-quality-scale/rules/${id}`;
                 const relatedRule = docs[`core/integration-quality-scale/rules/${id}`];
                 return (
                     <li key={id}>
-                        <Link to={`rules/${id}`}>{id}</Link> - {relatedRule.title}
+                        <Link to={absoluteRulePath}>{id}</Link> - {relatedRule.title}
                     </li>
                 );
             })}

docs/core/integration-quality-scale/index.md

@@ -94,7 +94,7 @@ Home Assistant encourages our contributors to get their integrations to the high
 
 When an integration reaches the minimum requirements for a certain tier, a contributor can open a pull request to adjust the scale for the integration.
 This request needs to be accompanied by the full checklist for each rule of scale (including all rules of lower tiers), demonstrating that it has met those requirements.
-The checklist can be found [here](checklist).
+The checklist can be found [here](/docs/core/integration-quality-scale/checklist).
 
 Once the Home Assistant core team reviews and approves it, the integration will display the new tier as of the next major release of Home Assistant.
 

docs/core/integration-quality-scale/rules/_includes/related_rules.jsx

@@ -8,10 +8,11 @@ export default function RelatedRules({relatedRules}) {
     return (
         <ul>
             {relatedRules.map((rule) => {
+                const absoluteRulePath = `/docs/core/integration-quality-scale/rules/${rule}`;
                 const relatedRule = docs[`core/integration-quality-scale/rules/${rule}`].title;
                 return (
                     <li key={rule}>
-                        <Link to={rule}>{rule}</Link>: {relatedRule}
+                        <Link to={absoluteRulePath}>{rule}</Link>: {relatedRule}
                     </li>
                 );
             })}

docs/core/integration-quality-scale/rules/action-setup.md

@@ -48,7 +48,7 @@ async def async_setup(hass: HomeAssistant, config: ConfigType) -> bool:
 
 ## Additional resources
 
-For more information on how to set up service actions, see the [service documentation](../../../dev_101_services).
+For more information on how to set up service actions, see the [service documentation](/docs/dev_101_services).
 
 ## Exceptions
 

docs/core/integration-quality-scale/rules/appropriate-polling.md

@@ -56,7 +56,7 @@ class MySensor(SensorEntity):
 
 ## Additional resources
 
-More information about polling can be found in the [documentation](../../../integration_fetching_data).
+More information about polling can be found in the [documentation](/docs/integration_fetching_data).
 
 ## Exceptions
 

docs/core/integration-quality-scale/rules/async-dependency.md

@@ -14,7 +14,7 @@ This results not only in a more efficient system but the code is also more neat.
 
 ## Additional resources
 
-More information on how to create a library can be found in the [documentation](../../../api_lib_index).
+More information on how to create a library can be found in the [documentation](/docs/api_lib_index).
 
 ## Exceptions
 

docs/core/integration-quality-scale/rules/config-entry-unloading.md

@@ -35,7 +35,7 @@ This can be useful to clean up resources without having to keep track of the rem
 
 ## Additional resources
 
-More information about config entries and their lifecycle can be found in the [config entry documentation](../../../config_entries_index).
+More information about config entries and their lifecycle can be found in the [config entry documentation](/docs/config_entries_index).
 
 ## Exceptions
 

docs/core/integration-quality-scale/rules/config-flow-test-coverage.md

@@ -60,8 +60,8 @@ async def test_full_flow(
 
 ## Additional resources
 
-More information about config flows can be found in the [config flow documentation](../../../config_entries_config_flow_handler).
-More information about testing integrations can be found in the [testing documentation](../../../development_testing).
+More information about config flows can be found in the [config flow documentation](/docs/config_entries_config_flow_handler).
+More information about testing integrations can be found in the [testing documentation](/docs/development_testing).
 
 ## Exceptions
 

docs/core/integration-quality-scale/rules/config-flow.md

@@ -69,7 +69,7 @@ class MyConfigFlow(ConfigFlow, domain=DOMAIN):
 
 ## Additional resources
 
-More information about config flows can be found in the [config flow documentation](../../../config_entries_config_flow_handler).
+More information about config flows can be found in the [config flow documentation](/docs/config_entries_config_flow_handler).
 More information about the architecture decision around config flows can be found in [ADR-0010](https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md)
 
 ## Exceptions

docs/core/integration-quality-scale/rules/devices.md

@@ -45,7 +45,7 @@ If the device represents a service, be sure to add `entry_type=DeviceEntryType.S
 
 ## Additional resources
 
-More information about devices can be found in the [device](../../../device_registry_index) documentation.
+More information about devices can be found in the [device](/docs/device_registry_index) documentation.
 
 ## Exceptions