I uploaded an image in asset library and imported that using below code in my LWC js file
import PLACEHOLDER_IMAGE from '@salesforce/contentAssetUrl/placeholderImage';
export default class CpFeatures extends LightningElement {
// Expose the asset file URL for use in the template
placeholderImage = PLACEHOLDER_IMAGE;
}
When I am pushing the code to the org I am getting
Exception while getting the content asset for reference
placeholderImage of type contentAssetUrl in file
Not exactly an answer, but something I found a few months back on React. React is also a web framework like LWC.
At Facebook, we use React in thousands of components, and we haven’t found any use cases where we would recommend creating component inheritance hierarchies.
Props and composition give you all the flexibility you need to customize a component’s look and behavior in an explicit and safe way. Remember that components may accept arbitrary props, including primitive values, React elements, or functions.
If you want to reuse non-UI functionality between components, we suggest extracting it into a separate JavaScript module. The components may import it and use that function, object, or a class, without extending it.
Src: Composition Vs Inheritance in React
TBH I too never faced a scenario where I had to extend my Custom Component, In case of JS reusability, It can be done importing service libraries, and markup extension? are just parent markup containing child markup.
I know about a consideration that pchittum answered few months back, that you cannot pass parent property while creating child component via App Builder.
It is because toast is not available for Mobile App
If you check the documentation, it says that toast is just available for Lightning Experience (one container) only
Comparatively, when you check the docs of pill, it is available for all containers - Lightning Experience, Lightning Communities, Salesforce Mobile App, Standalone Lightning App
Best Answer
I ran into the same issue. To fix it I added the contentassets to my vscode project, and then the deployment went through.