Ensuring that a user's personal workspace name is their first name by default.
This is because the full name makes the entire workspace name very long. If we just use the first name, it'll be a shorter string and easier to read by the end user as well.
See merge request theappsmith/internal-tools-server!142
This is because the full name makes the entire workspace name very long. If we just use the first name, it'll be a shorter string and easier to read by the end user as well.
Various api pane and dynamic input improvements
* Added an Allow HTML option for text widgets so that i can render HTML
* Input now sets the initial height on mound
* When input input is updated automatically, the cursor is set to the end of the input
* Input only shows error tooltip when it is in focus. The red border is still present
* Updated the stale property pane config in the codebase
* Api name placeholder updated to "API name (camel case)"
* Recursive binding search for dry runs
* If dynamic result is an object for action calls, convert it to string
* Fixed failing dry runs with dynamic bindings
See merge request theappsmith/internal-tools-client!217
Modifying the forgotPassword flow to send the email to the user with a clickable URL.
Also adding the domain to which we need to link to in the resetPassword POST body. This will ensure that we send a valid URL to redirect the user back to the client app to ensure that they can set a new password.
See merge request theappsmith/internal-tools-server!138
Logout feature
Logout
======
- User can logout from the organization dropdown in the scaffolding pages
- User will redirect to the login page on a successful logout
See merge request theappsmith/internal-tools-client!213
Feature/api cached response autocomplete
Uses the cached response in the action to show autocomplete hints
See merge request theappsmith/internal-tools-client!210
2. Only dependencies of actions over other actions are counted. If the action is dependent on widgets, thats is not counted as a dependency and is left for the frontend to handle.
Sending email to new user on signup
We now send a welcome email to the user when they signup on the Appsmith platform.
See merge request theappsmith/internal-tools-server!137
Fixing the bug where the custom authentication failure handler wasn't being invoked
This was because we need a custom authentication entry point to override the failure handler as well.
See merge request theappsmith/internal-tools-server!136
Modifying the logoutSuccessHandler to return success and failure JSONs instead...
Modifying the logoutSuccessHandler to return success and failure JSONs instead of redirecting the client to the login page
This allows the client to invoke the logout call via a XHR request instead of a form post.
See merge request theappsmith/internal-tools-server!135
Adding a logout handler to redirect the client back to the login page
Adding a logout handler to redirect the client back to the login page after the user logs out of the application.
Also refactoring all the custom authentication classes into a single package to make it code organization clearer.
See merge request theappsmith/internal-tools-server!133
Fixing bug where we shouldn't query the DB to find action and store cached result if it's a dry run
See merge request theappsmith/internal-tools-server!132
Bugfix: Returning only orgs that belong to a user
When the user lists the organizations for themselves, we should only return those orgs that belong to the user instead of all the organizations in the db.
See merge request theappsmith/internal-tools-server!131
Adding the redirect back to the client's index page on successful oauth2 login by the user
We use the referer header to find the client's endpoint and redirect to that endpoint once the OAuth2 login is successful. This is implemented via CustomServerOAuth2AuthorizationRequestResolver and AuthenticationSuccessHandler
See merge request theappsmith/internal-tools-server!130
We use the referer header to find the client's endpoint and redirect to that endpoint once the OAuth2 login is successful. This is implemented via CustomServerOAuth2AuthorizationRequestResolver and AuthenticationSuccessHandler
