You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have multiple places in Calypso that track permitted/enabled importers, including the following:
getConfig() and getImporters() in client/lib/importer/importer-config.tsx
The logic in getFinalImporterUrl() in client/landing/stepper/declarative-flow/internals/steps-repository/import/helper.ts includes a local productImporters constant
The ListStep component in client/blocks/import/list/index.tsx includes a hard-coded list of primary and secondary import platforms
Checklist
Confirm which platforms should be enabled during import flows
Confirm which location we're going to use as our source of truth
Update callers to use the primary location
Related
No response
The text was updated successfully, but these errors were encountered:
To help wrap my head around this a bit, I've created a spreadsheet of the different engines and locations in Calypso:
34b20-pb/#bash
It makes the most sense to me to consolidate everything into getConfig in lib/importer/importer-config.tsx. The other functions are using a subset of the data defined in getConfig so it seems reasonable that they can pull their data from getConfig instead.
We can also add a primary/secondary designation that the ListStep could use.
Details
We have multiple places in Calypso that track permitted/enabled importers, including the following:
getConfig()
andgetImporters()
inclient/lib/importer/importer-config.tsx
getFinalImporterUrl()
inclient/landing/stepper/declarative-flow/internals/steps-repository/import/helper.ts
includes a localproductImporters
constantListStep
component inclient/blocks/import/list/index.tsx
includes a hard-coded list of primary and secondary import platformsChecklist
Related
No response
The text was updated successfully, but these errors were encountered: