Skip to content

Conversation

@mattwbeard
Copy link
Contributor

Description

clarify the same setting should be applied across all types

Type of change

  • Fixes

clarify the same setting should be applied across all types
@vercel
Copy link

vercel bot commented Aug 19, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
codat-docs Ready Ready Preview, Comment Dec 23, 2025 5:26pm

@mattwbeard mattwbeard enabled auto-merge (squash) August 19, 2025 11:00
@github-actions
Copy link

Overall readability score: 57.88 (🟢 +0)

File Readability
advanced-sync-settings.md 66.58 (🟢 +1.26)
View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File Readability FRE GF ARI CLI DCRS
advanced-sync-settings.md 66.58 55.03 9.2 10.6 11.08 6.97
  🟢 +1.26 🟢 +0.1 🟢 +0.29 🟢 +0.2 🟢 +0.05 🟢 +0.12

Averages:

  Readability FRE GF ARI CLI DCRS
Average 57.88 48.57 10.36 11.58 12.12 7.83
  🟢 +0 🟢 +0 🟢 +0 🟢 +0 🟢 +0 🟢 +0
View metric targets
Metric Range Ideal score
Flesch Reading Ease 100 (very easy read) to 0 (extremely difficult read) 60
Gunning Fog 6 (very easy read) to 17 (extremely difficult read) 8 or less
Auto. Read. Index 6 (very easy read) to 14 (extremely difficult read) 8 or less
Coleman Liau Index 6 (very easy read) to 17 (extremely difficult read) 8 or less
Dale-Chall Readability 4.9 (very easy read) to 9.9 (extremely difficult read) 6.9 or less

## 💡 Tips and traps

- When using advanced sync settings, settle on a uniform approach across your data types, as we cannot guarantee consistency if different approaches are applied.
- When using advanced sync settings, settle on a uniform approach across your data types (e.g. all data types request 24 months' data). Some data types share requests, and applying different approaches may cause inconsistency.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Parens] Use parentheses judiciously.

## 💡 Tips and traps

- When using advanced sync settings, settle on a uniform approach across your data types, as we cannot guarantee consistency if different approaches are applied.
- When using advanced sync settings, settle on a uniform approach across your data types (e.g. all data types request 24 months' data). Some data types share requests, and applying different approaches may cause inconsistency.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.Latin] Use 'for example' instead of 'e.g.'.

@github-actions
Copy link

Link check results for preview deployment (https://codat-docs-git-updateAdvancedSyncSettingsTips-codat.vercel.app):

[
  "[404] https://codat-docs-git-updateadvancedsyncsettingstips-codat.vercel.app/"
]

@mattwbeard mattwbeard merged commit 00a0ce5 into main Dec 23, 2025
4 of 9 checks passed
@mattwbeard mattwbeard deleted the updateAdvancedSyncSettingsTips branch December 23, 2025 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants