Trying to deploy lightning component bundles, the lightning components are referenced on quick actions created and placed on account layout.
When I am trying to deploy the lightning component bundles, its threwing following deployment issues :
I have tried so many ways to fix the issues by adding/removing required attributes in lightning components, also tried to add/remove default values on attributes, but still has the same issue. Also tried to change the version on component from 38.0 to 37.0, but still no luck.
Can anyone help me on this? Thanks in Advance!!
Thanks,
Tarun
This is the workaround fixed my issue :
https://success.salesforce.com/answers?id=9063A000000DaazQAC
Related
What we want to do:
We have two projects:
A consumer focused frontend
A business focused dashboard
The frontend uses cool custom styling, while the dashboard is rather boring. The idea is that you can edit and create objects in the dashboard and then preview them in the styling of the frontend (imagine setting up an amazon product and then previewing it as the product page). Ideally we would also like to offer live editing, meaning you see the proper rendered product page and you can edit the information live.
Our Setup
Two separate repositories
Both use React + Tailwind
There are not many custom CSS classes as everything is styled via tailwind classes in the code
What would be the best solution?
I have a couple of solutions, that might work with more or less success (e.g. sharing components via bit.dev). Did someone built something similar or could recommend some best practices?
Depends on what is the best solution for you. What is best for you, might not be the best for me, or the other way around.
Bit is a way to share components. Components are isolated pieces of functionality (UI, Hooks, Themes, whatever) That can be used and consumed across several projects.
You could totally have a Bit workspace, where you design, create and edit your components, export them once finished, and consume them in both your repositories.
bit new react my-shared-components-workspace --default-scope LeonardCompany.LeonardRemoteScope
cd my-shared-components-workspace
bit create react shared-button
# edit your button
bit tag -m "initial tag" shared-button
bit export shared-button
In your repos:
npm install #bit/LeonardCompany.LeonardRemoteScope.shared-button
Want to update the button? Edit it again in your workspace, export, and update the projects. Ultimately, those projects could be App components too.
Let me know if it helped.
Recently I've joined a new job and they are working with Salesforce. They have all pages with APEX and I propose to migrate to Lightning components.
I've created the first 7 components and I'm using Atomic Design Methodology (https://atomicdesign.bradfrost.com/chapter-2/) to develop these components.
I want to implement stories (with Storybook) or another similar library to document and put examples of each web component.
My question is... Is it possible? I try to install Storybook in the project and isn't working. The question is simple, whether or not you can. And if not, if you know any alternative to it.
Thank you!
In order to use Storybook, you will need to follow the provided Storybook documentation for lightning "Web Component" rather than the other available options like React and configure your VS Code to work with your SF Environment. Also, you might want to look into downloading the lwc-services, lwc-webpack-plugin and mo-dx-plugin dependency.
I am trying to create a custom component in AEM's SPA editor for react. The custom component will only hold a parsys or a responsive-grid, where i can drag and drop components.
I can do it very easily in htl :
<sly data-sly-resource="${'parsys' # resourceType='foundation/components/parsys'}"></sly>
How can I implement it in react?
Adobe's reference implementation doesn't provide any solution for this though it provides Layout Container. I've gone through adobe's example and many others on internet, also checked the adobe experience league, but nothing useful found so far.
Any idea or solution would be appreciated.
Thanks in advance.
Right now I am working with Rocket.Chat and I need to make my own custom pages and CSS. I copied my rocketchat:ui package and renamed it to be childtheme:ui and changed the name of my package in my package.js file to match my package name. However, when I edit a page it still loads the original Rocket.Chat UI. I'm not exactly sure how I can do this, but I'd like to load my UI after the original UI is loaded. A Rocket.Chat developer told me to add a reference in one of my files: Package.use()
I don't know exactly where I can declare this reference or if this is even the best way to load my custom UI, but if anyone has experience I'd appreciate it! Thank you!
Are you sure it's Package.use() and not Package.onUse() ?
If your custom package is a copy of rocketchat:ui package, you should already have it.
Do your have your package declared in .meteor/packages ?
My team is creating the administration panel of a CMS using React, Typescript, TSX and Webpack. Each page of the administration panel has been created as a React component, and each page contains many other child components (one for each section).
The CMS distribution currently includes a bundled version of the javascript needed to run the web app, but not the original TSX files.
Now, we would like to make it possible to the developers using our CMS to extend the web app by
1) Injecting additional sections into the UI using a "slot-fill" approach
2) Possibly even overriding the existing sections rendering a different component in the same place.
<div>
<SidebarComponent />
<Section1Component />
<Section2Component />
// How to inject a possible PluginComponent here?
</div>
From the research we've conducted so far, there seem to be no "official" way to do this, so I'm wondering what would be the best approach in this case.
I am facing the same issue where I need a component from a plugin to interact with a component from another plugin with a hook system. I have a created a small codesanbox with the same approach adapted to your need.
Basically the approach is to create a injectedComponents.js at the root of your plugin that specifies in which plugin and area your component needs to be injected.
Here is ademo
single-spa has some good options in order to achieve this.
Please see if it can be help for you.
Microfrontends
Parcels
I am late to this but
Just create a utility class with registry function, and register each component to the registry (just dictionary of key value pair, where key is a constant and Value is the component). T
Then when you display a component in your base app, get it from the registry using a key. Then once you publish this whole base app as package ( make sure to export the utility registry). A user can register a component with the same name and override the default component.
For communication between totally independant components, you can use and EventEmitter