Legacy dependency error, how can I solve this error? - material-ui

I get the following error when trying to import a MUI component into my workspace, does anyone know why? and if there is a way to use that component?
error: legacy dependency "mui-org.material-ui.button" was imported to one of the files in "/tasks-workspace/tasks-scope/apps/to-do". this workspace is Harmony and therefore legacy components/packages are unsupported. remove the import statement to fix this error
enter image description here
I need to use that component to create my custom component with new props

Related

how to export then import a powerapps solution that has a canvas app using a custom component

I cannot seem to export then import a powerapps solution that has a canvas app that references a custom component. I'm using the powerapps portal to create the solution, where I add the canvas app that uses the custom component. When I export, download, and try to import the solution at this point it fails with the error:
error code 8004F036: The dependent component CustomControl (Id=xxx) does not exist. Failure trying to associate it with CanvasApp (Id=yyy) as a dependency. Missing dependency lookup type = EntityNameLookup.
If I first go to the solution and click 'add required objects' it will not add the custom component. If I manually add it, it shows it as added, but still after exporting, downloading, and importing, I get the same error. It would be great if someone knows the proper steps to get this working.
You will have to do this in 2 steps.
custom control (either you created on or you used from some 3 rd party) should be deployed (imported) to Target system. If it is managed solution from 3rd party then you might have solution.zip file use this and deploy to target system. If you created this custom control, then create separate solution and just add your custom control and deploy this solution.
Once custom control is imported, then deploy/import your powerapps solutions.

Issue migrating to material ui v5 using datepicker and next

Getting Module not found: Can't resolve 'luxon' when using LocalizationProvider with AdapterLuxon and Next
I'm hoping I have something setup incorrectly.
codesandbox with the issue:
https://codesandbox.io/s/package-test-chyxlo?file=/pages/index.js
Turns out I was reading the docs wrong. Mui provides the adapters out of the box but you still need to include the utility package that you want. In my case, luxon.

Device calendar plugin for Flutter

We are using the device_calendar plugin and we are trying to reproduce the example app in ours. Im running into one error that I dont understand. The error is on the "enum DayOfWeekGroup". It is undefined even though I am including the package import. I tried adding it manually from the example code but it exists outside of the example project so its causing issues.
the plugin is : device_calendar: ^3.0.0+1
The enum exists in src folder outside the example everything else is being pulled into the package from the import but this enum.
This feature is not in the plugin yet, the workaround is use DayOfWeek enum in place of DayOfWeekGroup just in case someone is messing with the new version of device Calendar plugin like I was :)

Error in add method from Wicket version 6.15

I have gotten all the latest jars installed for the Wicket 6.15. I can verify this in the Maven Dependencies directory.
For some reason, I feel it is still pointing to an older version of Wicket. I am getting strange errors with the add method from the MarkupContainer.
Using the quick-start example, in the HomePage class I am getting an error with:
add(new Label("message", "If you see this message wicket is properly configured and running"));
The error is:
The method add(Component[]) in the type MarkupContainer is not applicable for the arguments (Label)
Not sure why it is using Component[] as a argument and not Component... childs
as I am used to.
I am using Eclipse.
Check your import statements. You probably accidentally imported a different Label instead of org.apache.wicket.markup.html.basic.Label.

Only a type can be imported in Hook

We are trying to access a class in custom jsp hook LR 6.0.6.
Lets say in a display style of asset publisher we want to do some manipulation and add some content in the webcontent.
If we are adding a class in the custom jsp hook project and importing that on the display style then the following error is generated at run Time.
An error occurred at line: 6 in the generated java file
Only a type can be imported. com.sample.hook.AbcUtil resolves to a package
Pl let us know what can be done to get this accomplished. We need to have a class over there. So we can't change the requirement.
Have a look at below blog link, Think it might help you.
http://www.liferay.com/web/kzhang/blog/-/blogs/using-custom-java-classes-in-a-jsp-hook