b310-digital / better-hotkeys-for-zoho-crm Goto Github PK

We will need to store some settings:

• Zoho org
• Zoho location (.eu/.com)
• Maybe settings to disable certain shortcuts
• Maybe adjust shortcuts to your needs

How should these settings stored?

Further Notes

• Some hotkeys are not working properly for windows. Please see below.

Checklist

• Repair hotkey ALT + S
• Repair hotkey ALT + Shift + A

Further Notes

• Add contextual hotkeys e.g. plus one page in lead module by leveraging content scripts

https://developer.chrome.com/docs/extensions/mv3/content_scripts/

Checklist

• Add hotkey Alt+1 for first module, Alt+2 for second module
• Adjust Readme.md

Currently the chrome app uses plain javascript. I would like to use typescript.

Please check the following questions:

• Can we add nodejs with dependencies?
• Can we leverage typescript?
• How do we have to modify the setup?
• Is a docker setup necessary?

https://betterprogramming.pub/creating-chrome-extensions-with-typescript-914873467b65

Hint: Please do not use webpacker. Instead, make use of vite or esbuild.

• Contact module
• Deal module
• Account module
• Refactor url function to get the Zoho url in own service

Further Notes

• We will make the short cuts even simpler and take gitlab as inspiration, e.g. a for jumping to account module when possible
• Commands change data => should be harder to press

Checklist

• [ ]

• Open Zoho from everywhere in the Lead module, see shortcut list
• Only when extension is activated
• Out of scope: Context related hotkeys, e.g. on the third page + 1 page, send mail to lead etc

Further Notes

Currently, our settings part only takes care of the subdomain crm not crmsandbox. See code below to illustrate the problem:

  public static getZohoUrl = async (): Promise<string> => {
    const zohoLocation = (await chrome.storage.local.get("location")).location;
    const zohoOrgId = (await chrome.storage.local.get("zohoId")).zohoId;

    return `https://crm.zoho.${zohoLocation}/crm/${zohoOrgId}`;
  };

Checklist

• Add sandbox option to link
• Please make sure to update the privacy section accordingly. It includes saved data.

• Prepare description of plugin
• Decide extension name, e.g. SuperHotkeys for Zoho CRM
• ...

Further Notes

• To keep the scope of the first version small, we decided that the implementation of the global hotkeys should not consider the url of the active tab
• However, we already had added some code for this that we want to preserve in the attached pull request so that we are able to include this feature in the next version of the extension

Checklist

• When the active tab is on the Zoho CRM page, then the extension should not open a new tab

• How to add this add-on to chrome
• ...

Currently, eu is displayed in the beginning but not set as default as it looks. you need to switch the select box before it is saved.

As a user, I want to start right away after installing the extension. The less configuration the better.

Further Notes

• Instead of providing Zoho org id and location, it is easier to simply paste the Zoho url. we do the rest

• Zoho CRM has some built-in redirects that might be beneficial, e.g.:

  • https://crm.zoho.eu/crm/tab/Home/begin => https://crm.zoho.eu/crm/org20084925147/tab/Home/begin
  • https://crm.zoho.eu => https://crm.zoho.eu/crm/org20084925147/tab/Home/begin
  • https://crm.zoho.eu/crm/ShowHomePage.do => https://crm.zoho.eu/crm/org20084925147/tab/Home/begin

Checklist

• Discuss and think through what configs are actually needed

• Title seems to be hello world
• logo is hello world
• ...

Further Notes

• When uploading an extension to the Google Chrome store, the extension need to be compliant, see https://developer.chrome.com/docs/webstore/troubleshooting
• This task deals with making the extension as compliant as it can be before submitting the extension to the store

Checklist

• Double check if the extension needs the permission tab => remove it if it is not needed @gerardo-navarro
• Make the matching URLs for injecting the content-script more precise @gerardo-navarro

• Call react component as start
• Do view layouting there

Further Notes

• The popup currently looks a bit lonely. Add our icon and add more finished look and feel to options

Checklist

• Style popup
• Add hotkey informations in readme and extension explanation