Skip to content
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

Improve sync language for clarity #267

Open
zachspears opened this issue Jan 11, 2025 · 1 comment
Open

Improve sync language for clarity #267

zachspears opened this issue Jan 11, 2025 · 1 comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team.

Comments

@zachspears
Copy link

zachspears commented Jan 11, 2025

When setting up Sync settings for Square the language is confusing and ambiguous.

Image

The sentence "Choose where data will be updated for synced products" is confusing because it is unclear if it means:

  • Choose where data will be updated TO for synced products
  • Choose where data will be updated FROM for synced products

I think this language could be improved by simply adding the word "from." It could also be reworded entirely for better clarity:

"Choose the origin for updates to synced products."

Something like this would remove the ambiguity from the phrasing entirely. It is also confusing that even with this setting, you must check a box to "Enable to push inventory." I am not sure what the purpose of the first option is, if the second option must then also also be enabled. However, this is not as big of an issue. Thanks! :)

@zachspears zachspears added the type: enhancement The issue is a request for an enhancement. label Jan 11, 2025
@zachspears
Copy link
Author

Origin Ticket: 9269609-zd

@jeffpaul jeffpaul added type: good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. and removed type: enhancement The issue is a request for an enhancement. labels Jan 14, 2025
@vikrampm1 vikrampm1 added the priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team.
Projects
None yet
Development

No branches or pull requests

3 participants