Skip to content

Commit f3d859e

Browse files
committed
.
1 parent e77e861 commit f3d859e

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

app/dashboard/usage/page.tsx

+1-1
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ export default function UsagePage() {
5959
};
6060

6161
fetchData();
62-
}, [currentStripeCustomerId]);
62+
}, [currentStripeCustomerId, currentOwnerName, userId]);
6363

6464
const formatNumber = (value?: number) => {
6565
if (!value) return "-";

app/docs/coverage/CommonConfiguration.tsx

+2-2
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,8 @@ export function CommonSections({
7676
<div className="bg-gray-50 p-4 rounded-lg mt-4">
7777
<p className="text-gray-700">
7878
<strong>About LCOV:</strong> LCOV (Linux Code Coverage) is a standard format for code
79-
coverage data. It's pronounced "el-cov" and is widely supported by various tools and
80-
services.
79+
coverage data. It&apos;s pronounced &quot;el-cov&quot; and is widely supported by various
80+
tools and services.
8181
</p>
8282
</div>
8383
</div>

app/docs/coverage/flutter/page.tsx

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ export default function FlutterConfigurationPage() {
1414
<h2 className="text-2xl font-semibold mb-4 text-left">Framework Configuration</h2>
1515
<KeyRequirements />
1616
<p className="text-gray-600 mb-4">
17-
Flutter's built-in test framework can generate LCOV coverage reports.
17+
Flutter&apos;s built-in test framework can generate LCOV coverage reports.
1818
</p>
1919

2020
<CodeBlock code={pubspecYaml} language="yaml" filename="pubspec.yaml" />

app/docs/coverage/page.tsx

+4-4
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,14 @@ export default function DocsPage() {
88
<div className="space-y-8">
99
<section>
1010
<p className="text-gray-600 mb-6">
11-
Learn how to use GitAuto's Coverage Dashboard to identify and improve low test coverage
12-
in your codebase.
11+
Learn how to use GitAuto&apos;s Coverage Dashboard to identify and improve low test
12+
coverage in your codebase.
1313
</p>
1414
</section>
1515

1616
<section>
1717
<h2 className="text-2xl font-semibold mb-4 text-left">Requirements</h2>
18-
<p className="text-gray-600 mb-4">To use GitAuto's coverage analysis:</p>
18+
<p className="text-gray-600 mb-4">To use GitAuto&apos;s coverage analysis:</p>
1919
<ul className="list-disc list-outside space-y-2 text-gray-600 mb-6 ml-5">
2020
<li>Coverage report must be in LCOV format</li>
2121
<li>
@@ -63,7 +63,7 @@ export default function DocsPage() {
6363
className="block p-6 border rounded-lg hover:border-pink-600"
6464
>
6565
<h3 className="text-xl font-semibold mb-2">Flutter Testing</h3>
66-
<p className="text-gray-600">Flutter's built-in test framework</p>
66+
<p className="text-gray-600">Flutter&apos;s built-in test framework</p>
6767
</Link>
6868
</div>
6969
</section>

0 commit comments

Comments
 (0)