Amplication, an open-source platform for generating production-ready backend applications, has seen significant development activity focused on enhancing its plugin architecture and build management. The project, which leverages AI to automate backend development, continues to attract considerable interest with nearly 15k stars on GitHub.
Recent issues and pull requests (PRs) indicate a concentrated effort on improving .NET code generation capabilities and private plugin functionalities. The team has addressed several bugs related to .NET service generation, such as execution time (#8861) and method naming conventions (#8837). These issues suggest ongoing challenges in stability that the team is actively working to resolve.
Muly Gottlieb (mulygottlieb)
Yuval Hazaz (yuval-hazaz)
Mor Hagbi (morhag90)
Haim Bell (haimbell)
Amplication Bot (amplication-bot)
Dependabot (dependabot[bot])
Developer | Avatar | Branches | PRs | Commits | Files | Changes |
---|---|---|---|---|---|---|
Amplication Bot | 3 | 0/0/0 | 4 | 685 | 20708 | |
None (dependabot[bot]) | 4 | 8/0/4 | 4 | 2 | 6557 | |
Yuval Hazaz | 2 | 13/13/0 | 43 | 114 | 4862 | |
Muly Gottlieb | 2 | 9/8/1 | 26 | 70 | 1391 | |
morhag90 | 2 | 5/5/0 | 16 | 24 | 649 | |
None (haimbell) | 1 | 1/0/0 | 2 | 5 | 33 | |
amplication-engineering | 1 | 0/0/0 | 5 | 3 | 16 | |
Pavan Emani (p1kalys) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (amplication[bot]) | 0 | 14/0/14 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
Timespan | Opened | Closed | Comments | Labeled | Milestones |
---|---|---|---|---|---|
7 Days | 1 | 1 | 0 | 0 | 1 |
30 Days | 30 | 24 | 12 | 15 | 1 |
90 Days | 156 | 136 | 146 | 104 | 1 |
All Time | 3654 | 3029 | - | - | - |
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.
The Amplication GitHub repository has seen significant activity, with 625 open issues currently logged. Notably, several recent issues highlight ongoing bugs and feature requests related to the .NET code generation capabilities, indicating a focus on enhancing this aspect of the platform. A recurring theme is the need for better error handling and user feedback during the code generation process, particularly when using Jovu, the AI assistant.
Several issues have been raised regarding bugs in the .NET service generation, including problems with relation fields and incorrect method naming conventions. The presence of multiple bug reports suggests that while development is active, there may be underlying stability concerns that need addressing.
Issue #8861: 🐛 Bug Report: .NET DSG format execution time is too long
Issue #8851: 🐛 Bug Report: .NET build failed when using the Kafka Plugin
Issue #8838: NET DSG - Change all module action to PascalCase in PrepareContext
Issue #8837: 🐛 Bug Report: .NET DSG - Service.FIndOne - use method and types names from module actions and DTO
Issue #8829: 🐛 Bug Report: The wrong git details are used after deleting a plugin repository
Issue #8827: 🐛 Bug Report: Error details when private plugin is not available are not clear
Issue #8804: Bug (.NET): When disabling an entire module, the generated code has errors (missing "using" for Microsoft.AspNetCore.Mvc)
Issue #8803: Bug (.NET): Disabled actions are still generated in the controller
Issue #8799: dotnet-dsg: Update README.md file with instructions on how to build and run the generated code
Issue #8798: Update README.md file with instructions on how to run local
The concentration of recent issues around .NET functionality indicates a critical area for improvement within the Amplication platform. The repeated mention of bugs related to code generation suggests that users may face challenges when utilizing these features, which could hinder adoption and satisfaction.
Moreover, the documentation-related issues highlight a potential gap in user support materials, which could further complicate user experiences if not addressed promptly. The project team should prioritize resolving these bugs and enhancing documentation to improve overall usability and reliability of the platform.
The analysis of the pull requests (PRs) for the Amplication project reveals a total of 18 open PRs and 5037 closed PRs. The open PRs cover a range of updates, including refactoring, feature additions, dependency upgrades, and bug fixes. Notably, there is a significant focus on improving the user experience and enhancing the functionality of the platform.
PR #8860: Refactor/8840 program class
PR #8849: refactor(client): updated tooltips
PR #8846: chore(deps-dev): bump eslint-plugin-jsx-a11y from 6.7.1 to 6.9.0
PR #8845: chore(deps-dev): bump ts-loader from 9.4.4 to 9.5.1
PR #8844: chore(deps-dev): bump @storybook/jest from 0.1.0 to 0.2.3
PR #8826: chore(deps): bump fast-xml-parser, @aws-sdk/client-codecommit, etc.
PR #8757: feat(server): choose code generator on onboarding with Jovu
PR #8698: feat(server): add support for automatic subscription enroll on AWS Marketplace integration
PR #8315: chore(server): remove workspace migration scripts
PR #8054: fix(client): align plugin settings button to top right
PR #8053: refactor(client): separate the type exports
Additional PRs (#7983 to #7727) focus on various fixes and enhancements related to client features, server functionalities, and dependency management.
13-18. Closed PRs include significant updates and features such as private plugin handling, package management enhancements, and various bug fixes that contribute to overall project stability and functionality.
The current set of open pull requests reflects a strong emphasis on refactoring existing code for better maintainability and performance improvements through dependency upgrades. This indicates a proactive approach by the development team to ensure that the codebase remains modern and efficient while also addressing user experience concerns through UI adjustments and feature enhancements.
Several PRs are focused on enhancing user interaction with the platform, particularly through improved onboarding processes (e.g., selecting code generators) and better integration with AWS services for automatic subscription handling (#8698). The ongoing work suggests that Amplication is keen on making its platform more intuitive for new users while also streamlining backend processes.
A notable anomaly is the presence of several draft pull requests that have not seen recent activity (#8757, #8698). This could indicate potential bottlenecks in the development process or resource allocation issues that may need addressing to maintain momentum in feature development.
While there are numerous open pull requests, many have not been merged or reviewed promptly, which could lead to stagnation in feature deployment and bug fixes if not addressed soon. This could be a result of resource constraints or prioritization challenges within the team.
Some older PRs remain open without significant updates or reviews (e.g., PR #8315), which may require follow-up actions from maintainers to either progress these changes or close them if they are no longer relevant.
Overall, the current state of pull requests in the Amplication repository indicates active development with a clear focus on improving both functionality and user experience through thoughtful enhancements and necessary refactoring efforts. However, attention should be given to managing review processes effectively to prevent bottlenecks that could hinder progress in upcoming releases.
Muly Gottlieb (mulygottlieb)
Yuval Hazaz (yuval-hazaz)
Mor Hagbi (morhag90)
Haim Bell (haimbell)
Amplication Bot (amplication-bot)
Dependabot (dependabot[bot])
Feature Development:
Bug Fixes:
Testing:
Collaborations:
The development team is actively enhancing the Amplication platform with a strong emphasis on private plugin functionality and build management improvements. The collaborative environment fosters rapid development cycles while maintaining a focus on quality through testing and dependency management.