Fix widget boundaries persist issue
- FIX for - Widget boundaries persisted after dropping a new widget
See merge request theappsmith/internal-tools-client!251
UpdateLayout Null Pointer Exception : In case the layouts are null or the DSL is null, it should be handled gracefully.
See merge request theappsmith/internal-tools-server!165
New Widget drag effects
- Remove showPropertyPane, selectedWidget, focusedWidget, isDragging, isResizing, selectWidget, focusWidget from context
- Add the above to hooks and reducers.
- When dragging a new widget from the widget cards pane, widget boundaries show up
- When dragging a new widget from widget cards pane, the property pane closes.
See merge request theappsmith/internal-tools-client!247
Misc Fixes
- Change default button styles.
- Change input widget focus styles.
- Resize Restrictions
- Containers cannot resize vertically when children are obstructing
- All widgets will not resize below the rows and cols described in widget configs
See merge request theappsmith/internal-tools-client!246
Dropzone Snapping - Fix
- Earlier, the container padding was not taken into account when snapping the dropzones, now it is.
See merge request theappsmith/internal-tools-client!245
Converted Exceptions thrown in RestAPI plugin to Appsmith Plugin Exception so that its handled correctly.
See merge request theappsmith/internal-tools-server!162
Cleaning up the Github OAuth2 login flow by adding userNameAttribute to properties
This property helps define for Spring security which field in the OAuth2 user info to read in order to determine the username of the user. This is because this field is non-standard across different OAuth2 implementations. For each new OAuth2 provider that we support, this field will be required. Else the default name field will be picked up by Spring security (which is usually the id of the user).
See merge request theappsmith/internal-tools-server!156
This property helps define for Spring security which field in the OAuth2 user info to read in order to determine the username of the user. This is because this field is non-standard across different OAuth2 implementations. For each new OAuth2 provider that we support, this field will be required. Else the default name field will be picked up by Spring security (which is usually the id of the user).
Mock delete application which returns the application object which was being attempted to be deleted.
See merge request theappsmith/internal-tools-server!155
