-
Notifications
You must be signed in to change notification settings - Fork 9
Create Solving For Sheet Sync Failures Issues.md #352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
added the documentation + template sheet for anyone to use google sheets with app script to sync sheets as per their org's / program's requirements
WalkthroughA new documentation file has been introduced, detailing a Google App Script-based solution to address failures in syncing large Google Sheets with Glific for WhatsApp nudging campaigns. The document provides context, outlines limitations of existing sync methods, and offers step-by-step setup and configuration instructions for the proposed workaround. Changes
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
🚀 Deployed on https://deploy-preview-352--glific-docs.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (8)
docs/Use Cases/Solving For Sheet Sync Failures Issues.md (8)
1-1: Header is visually cluttered and harms readabilityThe excessive number of
entities stretches the header far beyond what’s necessary and can cause unpredictable wrapping on different screen sizes.
Recommend trimming it down to a simple “5-minute read · Advanced” pattern.
6-6: Run-on sentence—split for clarityThe summary line tries to convey too many ideas at once, making it hard to parse. Consider breaking it into two sentences:
-… this Google App Script method provides a scalable and reliable workaround. +… This Google App Script–based approach provides a scalable, reliable workaround. +It includes retries, logging, and notifications so you can reach your audience without manual intervention.
9-14: Parenthesis imbalance and minor grammatical issuesLine 13 opens a parenthetical but never closes it, and the clause is hard to follow.
-… (which means data pull for each teachers’ message to share data specific to observations made them, or journey undertaken by them in the LMS. +… (meaning Glific must pull data for each teacher to share personalised observations or LMS-journey updates).
15-17: Comma splice and wordingRemove the stray comma and tighten wording.
-The teachers across Nagaland and more geographies, need to access plans specific to them +Teachers across Nagaland and other regions need to access plans specific to them
20-21: Typo & wrong verb agreement“failt” → “fail” and “render these flows useless”.
-The problem arises when the sheets linked in these flows failt to auto-sync, which render these flows useless. +The problem arises when the sheets linked in these flows fail to auto-sync, rendering the flows useless.
28-28: Incorrect word: “useful” should be “useless”The sentence currently states the opposite of the intended meaning.
-… which means, the flows which use these sheet become useful and fail to send any content. +… which means the flows that use these sheets become useless and fail to send any content.
32-38: Minor wording & article usage“call sync a sheet” is awkward; “a AppScript” should be “an App Script”.
-Use the Glific APIs to call sync a sheet specific to your org. +Use the Glific APIs to trigger a sync for sheets specific to your org. -… by using time-driven “triggers” which is a AppScript functionality. +… by using time-driven “triggers”, an App Script feature.
63-66: Grammar & spelling fixes-Replace the “YOUR-NGO-SHORTCODE” with you the shortcode you use… +Replace “YOUR-NGO-SHORTCODE” with the shortcode you use… -Replace “YOUR-EMAIL-ID” on line 165 in order to get notifications to your email, incase this function fails. +Replace “YOUR-EMAIL-ID” on line 165 to receive failure notifications; use “in case” not “incase”.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/Use Cases/Solving For Sheet Sync Failures Issues.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/Use Cases/Solving For Sheet Sync Failures Issues.md
[grammar] ~20-~20: Ensure spelling is correct
Context: ...s when the sheets linked in these flows failt to auto-sync, which render these flows ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~65-~65: Consider a more concise word here.
Context: ... 5. Replace “YOUR-EMAIL-ID” on line 165 in order to get notifications to your email, incase...
(IN_ORDER_TO_PREMIUM)
added the documentation + template sheet for anyone to use google sheets with app script to sync sheets as per their org's / program's requirements
Summary by CodeRabbit