I am using the 4.1 backpack and I have a problem with the validation errors, they are not shown in the view, I have enabled GroupedErrors and InlineErrors, doing some tests I see that the problems come from my $fillable attributes, when they have more than 30 fields they are not show the group of errors, otherwise it is shown.
Does anyone know what could be causing this?
Related
"#material-ui/core": "4.12.3"
"#storybook/addon-storyshots": "6.3.12",
"#storybook/react": "6.3.12",
"react": "17.0.2",
Cannot use Dialog in a Storybook Storyshots test without errors, because the workarounds to get ReactDOM.createPortal and react-test-renderer to work together, causes the Material UI Dialog to throw console warnings in the tests.
I can workaround the first issue by either using the disablePortal property within Dialog stories or by mocking it out like this in testSetup:
jest.mock("react-dom", () => ({
...jest.requireActual("react-dom"),
createPortal: (children: ReactNode) => children,
}));
Both these workarounds create a second issue, which is for every story that contains a Dialog we get a console warning creating a huge amount of noise in the test output.
"Warning: Material-UI: the modal content node does not accept focus. For the benefit of assistive technologies, the tabIndex of the node is being set to "-1"."
I have checked for duplicates and have several related issues like this one, however, it's not the same as the actual Dialogs and Storybooks work fine with no errors and are composed properly with an internal focusable DialogContent. This issue is only affecting the storyshot tests when the portal is mocked or bypassed.
If I add the disableAutoFocus property to each Dialog within the Storybooks, the console warnings go away, however it seems like a hack.
Does anyone know why these warnings are appearing or a better way to resolve this?
Thanks
We use the ag-grid in different parts of our site and with protractor tests where a test opens a component that contains the ag-grid the test freezes and nothing happens anymore. The test case is not being completed.
This happens as soon as the ag-grid is getting initialized. If I remove the grid, then the test case continues fine. This behavior is the same in every location where we're using the ag-grid.
Is this an issue or what else could be wrong here?
I have not found a way around this, but I can tell you its related to the setTimeout underneath the hood. I wound up using browser.ignoreSynchronization = true, and then doing specific Waits with ExpectedConditions.presenceOf. Very sloppy and hopefully ag-grid fixes this at somepoint.
I have declared an EMF AbstractModelConstraint that checks some criteria. My problem is when the validation fails, the runtime workbench shows an error dialog. How can I prevent its appearance?
I found that the user can change this in Preference>Model Validation page. The validation message can be sent to the console view instead of popping up as a dialog.
I have a strange problem in JDeveloper 10g.
Some forms I can't see in View window, and therefore I can't select and edit properties in Poperty inspector, also in UI complete structure is missing.
Besides that form is working OK.
This one is OK.
How can I resolve this without the need for re-creation od forms?
Make sure you have the JBinit method in place. Compare a working form to a non-working one.
Problem was resolved with this changes.
I don't know yet what caused this form to be erroneously created.
//JScrollPane scPane = new JScrollPane(dataPanel); //This was surplus
//topPanel.add(scPane, BorderLayout.CENTER); //This was surplus
topPanel.add(dataPanel, BorderLayout.CENTER); //This was missing
I'm working on a plugin aiming to hide a swathe of menu contributions, then slowly reintroduce them to the UI according to how confident/experienced the user is, with help and introductory information given to the user at each step. So far I can happily hide menu contributions using activities. Getting them back has proved to be slightly more difficult, however.
I have menu contributions being hidden and shown via activities, but the problem I've run in to is that the menu isn't instantly updating to reflect the activites. When my provided variable is changed, the activities are being started/stopped appropriately, but the menu doesn't immediately change. That is, until you change view or perspective- actions which cause the menu to be refreshed.
I've tried calling refresh() on the MenuManager, as per this question, to no avail.
Obviously my expression is being evaluated immediately, but how can I get the menu itself to update/refresh immediately?
Thanks!
It turns out there were issues with fireSourceChanged().
Calling: fireSourceChanged(int sourcePriority, Map sourceValuesByName) doesn't work for me.
But calling fireSourceChanged(int sourcePriority, String sourceName, Object sourceValue) does work.
I really don't know why that is - could be an Eclipse bug??