sf-lwc-deploy-preexisting-design-flaw-dict-not-zip
sf_lwc_deploy was never functional — it builds a metadata_package dict (resembling a package.xml manifest) and passes it directly to mdapi.deploy() which expects a file path or IO[bytes]. The correct fix requires querying the LWC bundle and resource files from source via Tooling API, constructing a proper metadata zip with package.xml, then deploying via mdapi.deploy().
Related
- sf-lwc-deploy-passes-dict-not-zip-preexisting-design-flaw
- simple-salesforce-mdapi-deploy-expects-path-or-bytesio-not-b
- salesforce
- simple-salesforce-deploy-expects-filepath-not-base64
- simple-salesforce-deploy-expects-file-path-or-bytesio-not-ba
- salesforce-metadata-api-zip-no-src-prefix
- sfdc-retrieve-metadata-correct-api-usage
- salesforce-metadata-api-zip-root-paths-no-src-prefix
- salesforce-analytics-dashboard-create-api-expects-flat-json
- quotationextn-legacy-apex-api-v41-massive-class
- salesforce-quotation-car-park-excluded-from-av-computation
- qad-applied-offer-field-never-populated
- salesforce-metadata-api-zip-root-no-src-prefix
- salesforce-metadata-api-zip-must-have-no-src-prefix
- sf-lwc-deploy-required-full-rewrite-tooling-api-approach
- salesforce-restful-supports-both-data-and-json-kwargs