Appsmith is an open-source platform designed to streamline the creation of internal tools, admin panels, and dashboards by integrating with a variety of databases and APIs. Managed under the appsmithorg organization on GitHub, it boasts significant community involvement and extensive documentation support. The project's current trajectory shows active development with a focus on enhancing functionality and user experience.
These issues suggest vulnerabilities in version control integrations and core functionalities that could hinder user operations and trust in the platform's reliability.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 101 | 33 | 56 | 0 | 3 |
| 14 Days | 159 | 63 | 95 | 0 | 3 |
| 30 Days | 313 | 145 | 231 | 1 | 4 |
| All Time | 20773 | 17070 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Number | Title | Creator | State | Rating |
|---|---|---|---|---|
| #36166 | fix: Video2 spec flaky fix | Sagar Khalasi (sagar-qa007) | open 2024-09-06 | 3 |
| The pull request removes a flaky test case related to the Video Widget's muted functionality, which could be seen as a positive step towards reducing test flakiness and improving the reliability of the test suite. However, the removal of a test case rather than fixing or improving it might not address the underlying issue with the widget's functionality in automated testing environments. This change is somewhat significant as it affects the test coverage but does not introduce new features or substantial improvements to existing code. Therefore, it receives an average rating of 3. | ||||
| #36165 | Reactive binding | Vemparala Surya Vamsi (vsvamsi1) | open 2024-09-06 | 4 |
| The pull request introduces significant improvements and new features to the dependency management system, enhancing performance and modularity. It includes well-documented code changes, automated tests, and addresses a clear need within the project. However, it lacks a corresponding issue link for context and has minor areas for optimization suggested in review comments, which prevents a perfect score. | ||||
| #36161 | chore: makeParentDependedOnChildren optimisation only affected nodes in the graph is computed | Vemparala Surya Vamsi (vsvamsi1) | open 2024-09-06 | 3 |
| The pull request introduces a significant performance improvement by optimizing the dependency map computation, which is a positive aspect. However, it has failed some critical Cypress tests, indicating potential issues that could affect stability or functionality. The lack of corresponding issue linkage and incomplete documentation on the changes also detracts from its quality. Overall, while the optimization is valuable, the PR needs more work to ensure reliability and maintainability. | ||||
| #36158 | fix: remove Select key value selects, fix default | Ilia (znamenskii-ilia) | open 2024-09-06 | 2 |
| The pull request introduces some improvements in validation logic and refactoring, which are positive. However, it has significant drawbacks such as failing Cypress tests, which indicate that the changes may introduce new bugs or break existing functionality. Additionally, the lack of a linked issue for tracking and discussion of these changes is a concern, as it suggests a lack of thorough review or alignment with the project's requirements. The combination of these factors leads to a rating of 2, indicating that substantial improvements are needed before merging. | ||||
| #36156 | Do not merge : Run the test | Sagar Khalasi (sagar-qa007) | open 2024-09-06 | 3 |
| The pull request updates test specifications to focus on the 'JSON Form' component, which is a positive change for targeted testing. However, the PR is marked as 'Do not merge' and lacks a clear issue link or number, suggesting it might be incomplete or for demonstration purposes. The description and communication are well-documented, but the overall impact seems moderate without additional context on the necessity of these changes. | ||||
| #36151 | fix:Sort issue for action column in table. | Saicharan Pabbathi (saicharan-zemoso) | open 2024-09-06 | 3 |
| The pull request addresses a specific issue by removing sort functionality from action columns in a table, which is a clear and focused improvement. However, it's a relatively minor change in the context of the entire application and doesn't introduce any significant new features or complex logic. The implementation seems correct, and unit tests are added, which is good practice. Nonetheless, the change is not substantial enough to merit a higher rating, as it doesn't significantly enhance the overall functionality or performance of the application. | ||||
| #36140 | fix: hide datepicker clear button when date cell set to required | Shivam kumar (Shivam-z) | open 2024-09-06 | 4 |
| The pull request effectively addresses the issue of hiding the 'Clear' button on required date fields, enhancing user experience by preventing invalid form submissions. The changes are well-implemented with appropriate modifications to component properties and conditional rendering based on the 'isRequired' flag. However, it's a relatively minor feature enhancement, lacking broader impact or complexity that would merit a perfect score. | ||||
| #36132 | chore: External contribution PR test | Rishabh Rathod (rishabhrathod01) | open 2024-09-05 | 3 |
| The pull request introduces several changes to the Firestore plugin, including code refactoring and new test cases. However, it lacks a corresponding issue link, which is crucial for tracking the purpose and discussion around these changes. The PR is still in draft mode and has not been reviewed or tested by peers, as indicated by the automated comments. Additionally, the changes are mostly incremental improvements and refactoring without substantial new features or performance enhancements. | ||||
| #36131 | fix: disable loading button | Ilia (znamenskii-ilia) | open 2024-09-05 | 2 |
| The pull request introduces a logical fix by disabling the button when it is in a loading state, which is a positive change. However, the PR has significant issues as it has failed multiple critical Cypress tests related to various functionalities, indicating that the change may have introduced new bugs or broken existing features. This failure impacts the overall quality and reliability of the PR, making it necessary for further work and testing before it can be considered for merging. | ||||
| #36126 | feat: allow multiple lines in alert component | saiprabhu-dandanayak | open 2024-09-05 | 3 |
The pull request addresses a specific issue of allowing multiple lines in alert messages, which is a useful enhancement but not a major feature addition. The implementation includes both front-end changes and Cypress tests, indicating thoroughness. However, the use of cy.wait() in tests is a poor practice that could lead to flaky tests, and there are no significant architectural changes or challenging problems solved. The PR also had initial issues with lint and prettier checks, which were later fixed. Overall, this PR is solid but not exceptional. |
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Sagar Khalasi |  |
10 | 14/6/9 | 24 | 613 | 24714 |
| Ankita Kinger |  |
7 | 15/6/5 | 20 | 40 | 5221 |
| Alex |  |
5 | 6/2/3 | 14 | 15 | 2979 |
| Ilia |  |
4 | 4/2/1 | 5 | 62 | 2873 |
| Diljit (dvj1988) | 2 | 1/0/0 | 15 | 171 | 2685 | |
| albinAppsmith |  |
3 | 6/7/0 | 9 | 31 | 1441 |
| Manish Kumar |  |
1 | 6/6/0 | 5 | 11 | 1358 |
| Valera Melnikov (KelvinOm) | 2 | 2/0/3 | 6 | 242 | 1325 | |
| Hetu Nandu |  |
2 | 2/2/2 | 7 | 89 | 1264 |
| Pawan Kumar |  |
3 | 0/0/0 | 19 | 241 | 1242 |
| Pawan Kumar |  |
1 | 5/4/0 | 4 | 86 | 828 |
| Nilansh Bansal |  |
1 | 4/3/1 | 3 | 28 | 767 |
| Vemparala Surya Vamsi |  |
3 | 4/2/1 | 6 | 36 | 707 |
| Anna Hariprasad |  |
2 | 0/0/0 | 3 | 15 | 643 |
| Jacques Ikot |  |
2 | 2/3/0 | 6 | 10 | 444 |
| Rishabh Rathod |  |
3 | 4/1/1 | 7 | 19 | 412 |
| subratadeypappu |  |
2 | 2/1/0 | 7 | 21 | 405 |
| Naveen Goud |  |
1 | 1/0/0 | 2 | 4 | 387 |
| sneha122 |  |
1 | 5/4/1 | 4 | 16 | 361 |
| Anagh Hegde |  |
3 | 9/8/1 | 14 | 2 | 351 |
| Nidhi |  |
1 | 4/4/0 | 3 | 5 | 220 |
| Rudraprasad Das |  |
2 | 3/2/1 | 4 | 13 | 202 |
| Zachary Zondlo |  |
1 | 0/0/0 | 1 | 1 | 152 |
| Aman Agarwal |  |
2 | 15/3/11 | 5 | 8 | 149 |
| Rahul Barwal |  |
3 | 5/2/3 | 5 | 4 | 118 |
| Ashit Rath |  |
1 | 4/4/0 | 2 | 2 | 96 |
| Ayush Pahwa |  |
1 | 1/1/0 | 1 | 4 | 88 |
| NandanAnantharamu |  |
5 | 9/3/3 | 10 | 6 | 71 |
| Abhijeet |  |
2 | 4/3/0 | 4 | 6 | 62 |
| Saicharan Pabbathi |  |
1 | 2/1/0 | 1 | 4 | 61 |
| Apeksha Bhosale (ApekshaBhosale) | 1 | 1/0/0 | 1 | 1 | 51 | |
| Goutham Pratapa (pratapaprasanna) | 1 | 1/0/0 | 2 | 2 | 28 | |
| pewpewXD |  |
1 | 0/0/0 | 1 | 1 | 2 |
| yatinappsmith |  |
2 | 1/1/0 | 2 | 1 | 2 |
| Aparna Ramachandran (btsgh) | 0 | 1/1/0 | 0 | 0 | 0 | |
| N V N S Pavan Radha Krishna Kumar (Pavan134) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Shivam kumar (Shivam-z) | 0 | 2/0/0 | 0 | 0 | 0 | |
| Abhinav Jha (riodeuno) | 0 | 0/0/1 | 0 | 0 | 0 | |
| Laveena Enid (laveena-en) | 0 | 1/1/0 | 0 | 0 | 0 | |
| Raushan Kumar Gupta (raushan3737) | 0 | 2/0/0 | 0 | 0 | 0 | |
| None (shadabbuchh) | 0 | 1/1/0 | 0 | 0 | 0 | |
| Veera Venkata Siva Sai Vara Prasad Madine (PrasadMadine) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (RakshaKShetty) | 0 | 1/1/0 | 0 | 0 | 0 | |
| “sneha122” |  |
0 | 0/0/0 | 0 | 0 | 0 |
| None (phennapa-saeliw) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (saiprabhu-dandanayak) | 0 | 2/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The Appsmith project has a high level of activity with a total of 3,812 open issues and PRs. This indicates a vibrant and active community, as well as ongoing development efforts. The project utilizes TypeScript predominantly, which is common for robust web application frameworks.
Issue #36167: This issue involves a bug where users encounter an error when trying to import artifacts in a new Git branch. It is marked with several labels including 'Bug', 'Production', and 'Needs Triaging', suggesting that it affects the production environment and requires further investigation. This issue could potentially disrupt users' workflow, especially those relying on continuous integration and deployment processes.
Issue #36163 and Issue #36134: Both issues are related to critical bugs in the forking functionality of applications, where either queries are missing or datasources and queries do not appear post-forking. These are marked as high severity and affect the core functionality of the platform, potentially blocking users from successfully duplicating and using applications in new environments.
Issue #36150: Describes a medium severity bug related to prepared statements not working on first load. This could affect database interactions, leading to frustrating user experiences.
A recurring theme in the issues is related to integration and functionality with Git, indicating challenges in version control operations which are crucial for team collaboration in software development. Another significant area of concern is the forking functionality, suggesting possible improvements needed in handling application configurations during cloning processes.
#36167: [Bug]: Error Unable to import artifact in workspace When Creating New Git Branch
#36164: Fix flakiness of video2 spec due to third party
#36080: [Bug]: selectedRowIndex getting updated unnecessarily on data reload.
#36079: [Bug]: The table widget is no longer scrollable
These issues highlight critical areas affecting user experience and functionality, specifically in new feature branches and database interactions within the platform. The focus on resolving these issues could enhance stability and usability for end-users.
PR #36166: fix: Video2 spec flaky fix
PR #36165: Reactive binding
PR #36161: chore: makeParentDependedOnChildren optimisation only affected nodes in the graph is computed
PR #36158: fix: remove Select key value selects, fix default
PR #36156: Do not merge : Run the test
PR #36098: feat: Action redesign: Updating the config for MongoDB plugin to use sections and zones format
PR #36097: feat: Action redesign: Updating the config for Firestore plugin to use sections and zones format
This analysis provides a snapshot of ongoing efforts and challenges within the Appsmith project's development lifecycle, highlighting areas requiring attention or caution.
Summary
Quantified Reports
Detailed ReportsColorPickerComponentV2.tsxThis TypeScript file defines a React component named ColorPickerComponent which appears to be a customizable color picker for a UI library or application. It includes various features such as theme color selection, application-specific colors, and a full color picker mode.
ColorPickerProps defining props with appropriate types.isValidColor and isEmptyOrNill, which are likely imported from a utilities file, helping in keeping the code DRY.MAX_COLS), which is acceptable in this context but could be externalized into a configuration if they need to be reused or modified externally.any type (e.g., in the forwardRef definition). Providing more specific types would enhance type safety.The ColorPickerComponentV2.tsx file demonstrates good software engineering practices with clear structuring, adequate commenting, and effective use of external libraries. While there is some room for improvement in terms of refactoring and enhancing type safety, the overall quality of the code is high. This component should integrate well within a larger project assuming proper handling of props and state management aligns with the project's architecture.
The development team at Appsmith is actively engaged in both front-end and back-end improvements, focusing heavily on enhancing user experience, performance optimization, and robust testing. There is a clear emphasis on collaboration across different areas of the project, indicating a well-coordinated team effort. Continuous integration and deployment processes are being refined to ensure reliability and efficiency in delivering updates.