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
qkiroc		4	8/9/0	14	321	301961
liaoxuezhi		2	19/20/0	24	77	7291
SiynMa		1	3/2/1	4	8	524
Harry		1	0/1/0	1	4	72
jinye		2	0/0/0	3	5	68
hsm-lv		2	4/4/0	4	3	44
Allen		2	7/7/0	7	7	33
hezhihang		1	0/0/0	1	7	27
hzh11012		2	3/3/0	2	2	18
刘丹		1	0/1/0	1	5	13
gitforhlp		1	1/1/0	1	3	10
瓜娃子		1	1/2/0	1	1	10
chenwenhao		1	0/0/0	1	1	8
xiukun		1	0/1/0	1	1	6
F-jianchao		1	2/1/1	1	1	6
吴多益		1	1/1/0	1	1	5
lmaomaoz		1	4/4/0	1	1	5
thinkingc		1	2/2/0	1	1	2
dong		1	1/1/0	1	1	2
None (ChuHoMan)		0	1/0/1	0	0	0
Ikko Eltociear Ashimine (eltociear)		0	1/0/0	0	0	0
quirrel (donglixiaoche)		0	0/1/0	0	0	0

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

Report On: Fetch issues

Recent Activity Analysis

The recent activity in the GitHub issues for the baidu/amis project shows a diverse range of issues being reported, with a focus on usability, feature requests, and bug fixes. There are numerous reports related to the functionality of components like input-table, crud, and dialog, as well as requests for enhancements such as support for additional features in existing components.

A notable anomaly is the recurring issue with the input-table component, where users report performance degradation when handling large datasets (#10725, #10724). This suggests a potential bottleneck that could affect user experience in data-intensive applications. Another significant issue is the inconsistency in rendering behavior across different versions of amis, as seen in #10623 and #10418, which could indicate regression or compatibility challenges.

Themes among the issues include performance concerns with large data sets, requests for additional customization options (e.g., #10769), and integration challenges with other frameworks or libraries (e.g., #10730). The presence of numerous enhancement requests indicates active user engagement and a desire for more flexible and powerful features.

Issue Details

• #10866: Created 0 days ago. Priority: High. Status: Open. This issue involves real-time data change detection problems in the amis-editor-demo editor.
• #10863: Created 1 day ago. Priority: Medium. Status: Open. The issue discusses customizing prompt content during copy events.
• #10860: Created 1 day ago. Priority: Medium. Status: Open. Concerns about select component's "select all" feature not working with special characters.
• #10858: Created 1 day ago. Priority: Low. Status: Open. Request to move tree component's expand arrow icon behind the title.
• #10856: Created 2 days ago. Priority: Medium. Status: Open. Inquiry on disabling re-upload button functionality.
• #10855: Created 4 days ago. Priority: Low. Status: Open. Question on implementing dialog similar to toast using JavaScript methods.
• #10854: Created 4 days ago. Priority: Medium. Status: Open. Issue with pagination dropdown display position.
• #10853: Created 4 days ago. Priority: Medium. Status: Open. Problem with CRUD dialog column settings being synchronized across instances.
• #10852: Created 4 days ago. Priority: Low. Status: Open. Enhancement request for grouped tabs similar to overflow folding.
• #10851: Created 5 days ago. Priority: Low. Status: Open. Inquiry about open-sourcing amis-reports.
• #10850: Created 5 days ago. Priority: Medium. Status: Open. Issue with page refresh upon returning from navigation using SDK method.
• #10849: Created 5 days ago, Edited 2 days ago. Priority: High. Status: Open. Pie chart legend click leads to incorrect percentage display; question on upgrading echarts version.
• #10847: Created 6 days ago. Priority: Medium. Status: Open. Error after upgrading amis version in Vue3 project using veaury plugin.

These issues reflect ongoing development efforts and user feedback aimed at enhancing the functionality and reliability of the amis framework while addressing specific user needs and technical challenges encountered during its use in various environments and configurations.

Report On: Fetch pull requests

Overview

The dataset provides a list of open and closed pull requests (PRs) for the baidu/amis repository, a front-end low-code framework developed by Baidu. The repository is active with numerous PRs addressing various aspects of the project, including bug fixes, feature enhancements, and code optimizations.

Summary of Pull Requests

Open Pull Requests

1. #10867: A chore to correct a typo in saxes.ts.
2. #10581: A PR addressing data synchronization issues during action execution.
3. #10361: Fixes an issue with select components not clearing values on data change.
4. #9806: Addresses errors in Vue tabs and subform record options.
5. #9302: Fixes the delay property issue in the Spinner component.
6. #9301: Adds change event triggers to input-text selectors.
7. #9296: Fixes badge display issues in the Wizard component.
8. #9247: Enhances link components with max line display and tooltips.
9. #9235: Corrects table and CRUD row button position calculations.
10. #9214: Adds select actions to input-image components.
11. #9094: Fixes data update issues in nested pickers within inputTable components.
12. #9011: Adds support for GIF cropping in image components.
13. #8963: Improves CRUD and service store error handling.
14. #8697: Optimizes image gallery features and UI.
15. #8153: Adds text alignment options to CSS selectors in editors.
16. #8099: Completes missing theme parameters in amis-editor.
17. #8035: Adds a feature to clear default functions in InputFormula components.
18. #7074: Introduces circular event action checks.

Closed Pull Requests

1. #10865 & #10864: Style optimizations for dropdown conditions to prevent overflow.
2. #10862: Fixes errors in diffEdit functionality.
3. #10861: Corrects arrow display issues in collapsible components.
4. #10859: Adjusts rich-text loading positions.
5. #10857: Introduces read-only mode for editors with diff editor support.
6. #10846 & #10843: Fixes drag-and-drop and file rendering issues in OfficeViewer examples.
7. #10841 & #10838 & #10836: Resolves cascading selector data source label errors leading to crashes.
8. #10834 & #10833 & #10832: Various documentation updates and spelling corrections.

Analysis of Pull Requests

The baidu/amis repository shows a vibrant development environment with numerous active pull requests addressing a wide range of issues from minor bug fixes to significant feature enhancements.

Themes and Commonalities

• Bug Fixes: A substantial portion of the PRs focus on resolving bugs, such as fixing UI glitches (#10861), correcting functionality errors (#9302), and addressing data synchronization problems (#10581). This indicates a strong emphasis on maintaining software reliability and user experience.
• Feature Enhancements: Several PRs introduce new features or improve existing ones, like adding change events to input-text selectors (#9301) and optimizing image gallery functionalities (#8697). These enhancements suggest ongoing efforts to expand the framework's capabilities and usability.

Anomalies and Disputes

• Some PRs have been open for extended periods without resolution, such as #9806 (open for 172 days) and #7074 (open for 459 days). This could indicate complex issues or disagreements on implementation approaches that require further discussion or prioritization.

Lack of Recent Merge Activity

• While many PRs are actively being merged, some older PRs remain open, possibly due to lower priority or resource constraints.

Code Quality and Review Process

• The presence of labels like "request-changes" indicates an active review process where contributors are encouraged to refine their submissions before merging, ensuring code quality and adherence to project standards.

Overall, the baidu/amis project demonstrates a well-maintained open-source initiative with continuous improvements driven by community contributions, focusing on enhancing both functionality and user experience while addressing technical debt through bug fixes and optimizations.

Report On: Fetch commits

Development Team and Recent Activity

Team Members and Activities

hzh11012

• Recent work includes styling optimizations for dropdowns to prevent overflow issues.
• Collaborated with hezhihang.

liaoxuezhi (2betop)

• Active in multiple areas including bug fixes, feature enhancements, and code optimizations.
• Worked on version bumps, fixing display issues in collapsible components, and addressing various rendering problems.
• Collaborated with jinye and others.

CheshireJCat

• Fixed an issue with collapsible component arrow displays.
• Collaborated with jinye.

Allen (allenve)

• Focused on UI styling improvements and bug fixes related to rich-text loading positions.
• Worked on mobile style fixes for user-select components.

qinhaoyan (qkiroc)

• Contributed to expanding editor functionality and supporting read-only modes.
• Engaged in bug fixes and feature enhancements across multiple components.

hsm-lv

• Involved in fixing bugs related to input tags and configuration panels.
• Merged several pull requests focusing on bug resolutions.

elephantme

• Made minor documentation corrections.

gitforhlp

• Addressed spelling errors in documentation files.

nwind

• Fixed issues in OfficeViewer component related to file rendering.

jinye

• Collaborated on fixing collapsible component issues and other rendering problems.

F-jianchao

• Fixed issues with number input components regarding percentage handling.

hezhihang

• Worked on default settings for custom conditions in forms.

wibetter

• Upgraded ECharts version in the project dependencies.

Tatekii (SiynMa)

• Added unit tests for input tables and fixed related logic issues.

thinkingc

• Addressed popover display issues when covered by modals.

Patterns, Themes, and Conclusions

1. Active Bug Fixing: The team is actively engaged in resolving various bugs, particularly those affecting UI components such as dropdowns, collapsibles, and input elements. This indicates a focus on improving user experience and interface stability.

2. Collaborative Efforts: Many commits are co-authored or involve collaboration between team members, highlighting a collaborative development environment. This is evident in joint efforts by members like hzh11012 with hezhihang, and CheshireJCat with jinye.

3. Feature Enhancements: There is ongoing work to enhance existing features, such as expanding editor capabilities and improving styling options. This suggests a commitment to evolving the platform's functionality alongside maintaining its current features.

4. Documentation Updates: Minor updates to documentation indicate an attention to detail in ensuring that project information remains accurate and helpful for users.

5. Version Management: Regular version bumps and dependency updates are being managed by team members like liaoxuezhi, ensuring that the project stays up-to-date with external libraries and tools.

Overall, the team is actively maintaining the project through bug fixes, feature enhancements, collaborative efforts, and regular updates.