Invite Users
Organization Dropdown
=====================
- User must be able to see
- The organization dropdown in the headers
- The name of the organization in the header
- A list of navigation options on clicking the header; in a dropdown
- Navigate to the organization settings page on clicking "Organization Settings"
- View a list of organizations on clicking "Switch Organization"
Invite Users Form
=================
- User must be able to
- View the Invite Users header
- Go back to the previous page on clicking "Cancel"
- Add a list of email addresses in the User emails field by "Enter", "Space" and ","
- Delete individual email address - by clicking on the close icon, and "Backspace"
- Select a role for the set of emails
- See a validation message for each of the user email fields and role select fields
- Delete an entry of the "role -> emails" set by clicking on the "delete" icon at the end of each sets of fields
- Add another "role -> emails" set by clicking on "Add more"
- Submit the list of sets of " role -> emails" by clicking on Invite Users button
Other changes
=============
- Each of the protected pages will check for login on load
- When logged in and trying to access "/" (base URL), user will be redirected to the applications page
- User can navigate to the invite users page from the "Organization settings" page.
- Add black favicon for scaffolding pages, and orange for editor
See merge request theappsmith/internal-tools-client!203
Fix#418: Delete and Edit widget controls are functioning properly
- Delete and Edit controls for the selected widget were getting overlapped by the widgetName element, which is now fixed.
See merge request theappsmith/internal-tools-client!201
Fix#413: Adhere widget name and controls to designs
- Widget Name now adheres to designs
- Position and sizes of widget controls now adhere to designs.
See merge request theappsmith/internal-tools-client!198
Selected Option is now available in dropdown widget.
Fixes#383
Added a concept of derived properties for widgets. A derived property is something that is not stored in dsl because it can be evaluated from stored properties. For example: We do not need to store a `selectedOption` for a dropdown because it can be derived from `selectedIndex` and `options`. Similarly we do not need to store `selectedRow` in a table because it can be derived from `tableData` and `selectedRowIndex`.
Such properties are constructed on the fly for their usage in js execution and autocomplete.
To add a derived property to a widget add `getDerivedPropertiesMap` function which returns an object like this:
```
{
<DerivedPropertyName>: (widgetData: FlattenedWidgetProps) => {<<Implements how the derived property is evaluated.>>}
}
```
See merge request theappsmith/internal-tools-client!191
User Auth Flow
The following user scenarios are implemented:
Login
=====
- User should be able to login using email and password
- - Known issue: No redirect happens after login. In fact, an error shows. User should go to `/applications` manually
- User should be able to login using google
- - Know issue: User redirects to the `release` application or `production` applications. If you're using `release` or `production`, you'll be on the same domain.
- User should be able to see validation errors on login page for email and password
- Login button is in loading state when clicked (logging In)
- Login page should start with login button disabled
- Login page shows login errors, if any.
- User should be able to redirect to signup page from the link in the page
- User should be able to redirect to forgot page from the link in the page
- If the email field has any value, the value is carried over to forgot password page.
Sign Up
=======
- User should be able to sign up with email and password
- User should be able to see success message on successful signup.
- User should be able to see password and email validation errors.
- The signup button should work exactly the way it works in the login page
- User should be able to go back to login page from the link on the page.
Forgot Password
===============
- User should be able to see the email field populated if they had something in the email field on the login page. Works only when redirecting from login page's forgot password link.
- User should be able to see validation messages
- User should be able to initiate a request to send a reset token to their provided email
- The reset button should work exactly the way it works on the login page
- User should see the success and failure messages, with actionable links.
Reset Password
==============
- User should be able to reset their password
- User should be able to see success/failure messages with actionable links.
- User should be able to see validation errors.
- User should be able to go back to login page in case they change their mind.
Other changes
=============
- User should see proper error messages when we have a 500 error in forms
- User should redirect to login page if trying without a logged in session on protected routes (for eg: `applications/`)
- Custom form error message tag component which adheres to appsmith's intent colors.
See merge request theappsmith/internal-tools-client!177
Separate loading states per action
Fixes: #320, #273
* Fixes issue where loading state of one action is shared with others
* Adds a loading overlay when saving an action
See merge request theappsmith/internal-tools-client!188
