Quantify Issues

Recent GitHub Issues Activity

_{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.}

Quantify commits

Quantified Commit Activity Over 30 Days

Developer	Avatar	Branches	PRs	Commits	Files	Changes
1ilit		1	1/1/0	27	37	2754
Soumya Ghosh		1	1/1/0	1	2	231
Luis Carlos		1	1/1/0	9	5	206
IloGus		1	1/1/0	1	1	4
Tamás Balog		1	1/1/0	1	1	3
XC		1	1/1/0	1	1	1
Nopandi1101 (Nopandi1101)		0	1/0/1	0	0	0
Ali Salehi (alisalehi1380)		0	1/0/1	0	0	0

_{PRs: created by that dev and opened/merged/closed-unmerged during the period}

Report On: Fetch issues

Recent Activity Analysis

The DrawDB GitHub repository has seen significant recent activity, with 50 open issues currently logged. A notable trend is the prevalence of bugs related to SQL import functionality, particularly with PostgreSQL and MySQL. This indicates potential weaknesses in the parser or compatibility issues that could hinder user experience.

Several issues exhibit common themes, particularly around SQL import failures, such as missing support for specific data types and constraints. The urgency of these issues is underscored by the fact that many users report critical bugs affecting their ability to utilize the tool effectively.

Issue Details

Most Recently Created Issues

1. Issue #246: [BUG] Export SQL source error

   • Priority: High
   • Status: Open
   • Created: 1 day ago
   • Description: Postgres comments cannot be imported.

2. Issue #243: [BUG] Import fails on CREATE FUNCTION in Postgres SQL file

   • Priority: High
   • Status: Open
   • Created: 4 days ago
   • Description: The SQL import fails when encountering 'CREATE FUNCTION' syntax.

3. Issue #242: [BUG] Import fails on casting of a regex (Postgres SQL file)

   • Priority: High
   • Status: Open
   • Created: 4 days ago
   • Description: A Postgres SQL import fails at a specific location due to regex casting.

4. Issue #241: [BUG] Import fails on PG comments

   • Priority: High
   • Status: Open
   • Created: 4 days ago
   • Description: Importing a Postgres SQL file fails when encountering comments.

5. Issue #235: [BUG] MySQL, Import from SQL TEXT parsing fail

   • Priority: Medium
   • Status: Open
   • Created: 19 days ago
   • Description: Issues with importing TEXT datatype in MySQL.

Most Recently Updated Issues

1. Issue #235: [BUG] MySQL, Import from SQL TEXT parsing fail

   • Last Updated: 16 days ago

2. Issue #242: [BUG] Import fails on casting of a regex (Postgres SQL file)

   • Last Updated: 4 days ago

3. Issue #243: [BUG] Import fails on CREATE FUNCTION in Postgres SQL file

   • Last Updated: 4 days ago

4. Issue #241: [BUG] Import fails on PG comments

   • Last Updated: 4 days ago

5. Issue #217: [FEATURE] add BaseTable tool for convenience

   • Last Updated: 26 days ago

Analysis of Themes and Anomalies

The majority of recent issues are centered around bugs related to SQL imports, particularly with PostgreSQL and MySQL databases. This suggests that users are facing significant challenges when trying to import existing database schemas into DrawDB, which could deter new users or frustrate existing ones.

Moreover, the recurring nature of these issues indicates potential inadequacies in the current implementation of the SQL parser or a lack of comprehensive support for various SQL features across different database systems.

The presence of feature requests alongside bug reports highlights a community eager for enhancements but also points to a need for stability in core functionalities before expanding feature sets.

The active engagement from users in reporting these issues reflects a committed user base, but it also signals that the development team may need to prioritize resolving these critical bugs to improve overall user satisfaction and retention.

Report On: Fetch pull requests

Overview

The analysis of the pull requests (PRs) for the DrawDB project reveals a vibrant and active development environment. The project has seen significant contributions in terms of feature additions, bug fixes, localization efforts, and enhancements to user experience. The PRs cover a wide range of topics, from adding support for new languages to implementing features like PWA support and SQL export functionalities.

Summary of Pull Requests

Open Pull Requests

• PR #214: Moved router to a separate folder for better code readability. This PR aims to improve code organization and maintainability.
• PR #192: Added support for exporting SQL as OracleDB SQL. This feature expands the tool's compatibility with different database systems.
• PR #181: Add Azerbaijan Language Localization. This PR contributes to the project's internationalization efforts by adding support for the Azerbaijani language.
• PR #175: Highlight when editing relationship. This enhancement improves user interaction by providing visual feedback during editing.
• PR #155: Change theme options to dark theme switch. This PR simplifies the theme switching mechanism in the application.
• PR #152: Add offline PWA support. This feature enhances the application's usability by allowing offline access.
• PR #124: Refactor component structure of modal. This PR aims at improving code structure and reusability within modal components.
• PR #82: Added PWA, Installed lib vite-plugin-pwa. This PR marks the initial effort towards making the application a Progressive Web App (PWA).
• PR #42: Add functionality to convert JSON schema to Django models. This feature adds significant value by enabling integration with Django applications.

Closed Pull Requests

• PR #240: Fix casing do not match warning. A minor fix addressing Docker build warnings.
• PR #239: Add pushToGithub Feature. Proposed feature to upload SQL code to GitHub, but was not merged due to security concerns.
• PR #236: Fix fitWindow not finding element id. A bug fix that enhances functionality related to window fitting.
• PR #237: Create Yang gw 🙏. A non-functional PR that was closed without merging.
• PR #234: Implement file sharing using gists. Adds functionality for sharing diagrams via GitHub gists but was closed without merging.
• PR #229: [Feature] Add Documentation Menu with Markdown Export for Database Documentation. Enhances documentation capabilities but was closed without merging.

Analysis of Pull Requests

The analysis of open and closed pull requests for the DrawDB project highlights several key themes:

1. Active Development and Feature Expansion:

   • The presence of PRs like #192 (OracleDB SQL export) and #152 (PWA support) indicates ongoing efforts to expand the tool's capabilities and improve user experience.

2. Localization Efforts:

   • Multiple PRs (#181, #155) focus on adding new languages and improving existing translations, reflecting the project's commitment to accessibility for a global audience.

3. Community Engagement and Contribution:

   • The variety of contributors and the range of topics covered in PRs suggest an active community involvement in the project's development.

4. Focus on Usability and User Experience Enhancements:

   • Several PRs (#175, #124) aim at improving user interaction and interface elements, indicating a strong focus on usability.

5. Security and Maintenance Concerns:

   • Closed PRs like #239 highlight challenges related to security when introducing new features, emphasizing the need for careful consideration of security implications in development.

6. Diverse Range of Contributions:

   • Contributions range from minor bug fixes (#240) to significant feature additions (#192), showcasing a diverse range of community contributions that enhance both functionality and stability.

In conclusion, the DrawDB project benefits from a robust community that actively contributes to its development through feature enhancements, localization efforts, and usability improvements. The project's focus on expanding its capabilities while ensuring security and usability reflects its commitment to providing a valuable tool for database design globally.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Activities

1. 1ilit

   • Recent Activity:
   • Merged multiple branches and pull requests, including fixes for import issues, localization updates, and enhancements to the EditorCanvas.
   • Significant contributions to bug fixes, such as resolving import failures and handling incorrect links.
   • Implemented features like file sharing using gists and support for special values in PostgreSQL defaults.
   • Total: 27 commits with 2754 changes across 37 files.

2. IloGus (ilogus)

   • Recent Activity:
   • Contributed a fix for casing mismatch in the Dockerfile.
   • Total: 1 commit with 4 changes across 1 file.

3. ewqazxc

   • Recent Activity:
   • Fixed an issue with the fitWindow function not finding element IDs.
   • Total: 1 commit with 1 change across 1 file.

4. LuigimonSoft

   • Recent Activity:
   • Made multiple contributions including adding new translations and fixing export issues related to documentation.
   • Total: 9 commits with 206 changes across 5 files.

5. i-m-soumya

   • Recent Activity:
   • Added Bengali language support.
   • Total: 1 commit with 231 changes across 2 files.

6. picimako

   • Recent Activity:
   • Updated Hungarian translations.
   • Total: 1 commit with 3 changes across 1 file.

7. alisalehi1380 and Nopandi1101

   • Recent Activity:
   • No recent commits or changes reported.

Patterns, Themes, and Conclusions

• Active Development: The primary contributor, 1ilit, is heavily involved in both feature development and bug fixing, indicating a strong leadership role within the team.
• Collaboration: There is evident collaboration among team members, particularly in merging pull requests that address localization and functionality improvements.
• Localization Focus: Multiple commits from different contributors suggest a concerted effort to localize the application for a broader audience, enhancing its usability across different languages.
• Bug Fixes vs. Features: The recent activity shows a balanced focus on both fixing existing issues and implementing new features, which is crucial for maintaining software quality while evolving the product.
• Community Engagement: The presence of numerous pull requests indicates an active community contributing to the project, enhancing its robustness and feature set.

Overall, the development team demonstrates a proactive approach to both feature enhancement and maintenance of DrawDB, ensuring it remains user-friendly and accessible to a diverse audience.