The tooltip message for the summary generation feature has been enhanced. It now clearly mentions the need for the user to be logged in and have cloud sync enabled specifically for the project.
Changes:
- Tooltip message for the summary generation feature now reads "Summary generation requres that you are logged in and have cloud sync enabled for the project", making it context-specific and more informative.
This commit ensures the context menu triggers even when 'line.afterLineNumber' is null. It does this by checking if 'line.afterLineNumber' is not null, and if it is, it uses 'line.beforeLineNumber' instead.
Details:
- Replaced direct usage of 'line.afterLineNumber' with a conditional operator checking the value.
- If 'line.afterLineNumber' is not null, it will be used.
- If 'line.afterLineNumber' is null, 'line.beforeLineNumber' will be used instead.
This commit brings several notable changes which majorly include updating the SVG sizes and dynamic UI updates based on user inputs. Some unnecessary lines of code have also been removed to enhance the code's efficiency.
Detailed Changes:
- The SVG width and height have been changed from 14 to 20 for better visibility.
- Svelte contexts and event handlers have been added to respond to user interactions such as mouse events and fetch operations.
- The import line including `{ base } from '$app/paths'` in the second part of the diff has been removed.
- HTML classes have been manipulated for a streamlined experience making the UI responsive.
- Introduces a refreshing icon that spins while fetching is in progress.
- Several changes inside the div tags for a better UX by enriching user feedback on hover and click actions.
- Removed lines setting the behind variable within the script block.
- Other changes include updating dynamic variables used in the DOM, tweaking UI colors and backgrounds.
The revised code now allows the function parseFileSections to return hunkSections even if there is no file content. This appears to have resolved an issue where the function would return an empty array if the content was missing, hence potentially ignoring changes that have been stored in hunkSections.
Changes include:
- An early return statement has been moved further down in the code in the parseFileSections function.
- Now, even if file content does not exist, hunkSections are returned to the caller, ensuring that the changes are not missed.
This code change refactors the functions `git_remote_branches_data` and `get_base_branch_data` for improved concurrency and error handling. It primarily uses the `join_all` method from the Futures crate to effectively manage concurrent tasks.
Summary of changes:
- User avatars are now fetched concurrently rather than sequentially. This will improve performance when dealing with large numbers of authors.
- Introduced error handling when a proxy request for the gravatar image fails. A failure to retrieve the image will now default to the use of the original image url, instead of breaking the function.
- Removed redundant construction and use of a HashMap for managing proxies.
- Streamlined the `get_base_branch_data` function for better readability by eliminating the mutable `proxy_map` and directly calling the proxy in the async block.
- Optimized the creation of `virtual_branches::BaseBranch` and `virtual_branches::RemoteBranch` instances by directly embedding the changes within the `join_all` function calls, reducing the complexity of the code.
Redesigned the user profile page to receive Full Name instead of First and Last name. The user update method was adjusted to handle this change. Inputs in the UI that took the first and last name as separate inputs have also been modified to only accept a single name input.
Here's a summary of what was changed:
- The First Name and Last Name fields were replaced with a Full Name field in the form.
- The functions that submitted or processed first and last name data have been simplified to process full name data.
- The client-side and server-side code handling the user update has also been updated to handle only full name.
- Any relevant variable names were also updated to reflect this change.
- The user object now only checks and assigns the `name` property, instead of `given_name` and `family_name`.
As a note, this simplifies the form and the process but some user's may find the change limiting if they typically prefer to provide their names separately for their first and last names.
