amplication

šŸ”„šŸ”„šŸ”„ The Only Production-Ready AI-Powered Backend Code Generation

OTHER License

Downloads
864
Stars
15.2K
Committers
285

Bot releases are visible (Hide)

amplication - v1.5.1

Published by levivannoort over 1 year ago

amplication - v1.5.0

Published by levivannoort over 1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.7...v1.5.0

amplication - v1.4.7

Published by overbit over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.6...v1.4.7

amplication - v1.4.6

Published by overbit over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.5...v1.4.6

amplication - v1.4.5

Published by EugeneTseitlin over 1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.4...v1.4.5

amplication - v1.4.4

Published by tupe12334 over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.3...v1.4.4

amplication - v1.4.3

Published by EugeneTseitlin over 1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.2...v1.4.3

amplication - v1.4.2

Published by abrl91 over 1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.1...v1.4.2

amplication - v1.4.1

Published by tupe12334 over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.4.0...v1.4.1

amplication - v1.4.0

Published by levivannoort over 1 year ago

Smart git pull request strategy

As we work on improving the pull request and building the experience for our users, we are changing the pull request flow to take care of several issues we encounter.

Conflicts resolution

In the previous behavior of the smart git strategy, the custom code of the user will be overwritten in the amplication branch for each new commit. As a result, the conflict that the user had previously resolved would re-appear after each new commit. This release changes that behaviour, the user's custom code will be set aside from the branch into a temporary file and will be applied after the default commit. In that way, the user's custom code is given the "upper hand" so that the conflict had been resolved previously will not show again unless the amplication code is changed by the user.

Commit structure

Additionally the pull request that are created on a (re-)build of the project has been altered. The body and comments of the pull request should provide the user with more information.

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.3.5...v1.4.0

amplication - v1.3.5

Published by overbit over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.3.4...v1.3.5

amplication - v1.3.4

Published by overbit over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.3.3...v1.3.4

amplication - v1.3.3

Published by overbit over 1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.3.2...v1.3.3

amplication - v1.3.2

Published by overbit over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.3.1...v1.3.2

amplication - v1.3.1

Published by overbit over 1 year ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v1.3.0...v1.3.1

amplication - v1.3.0

Published by overbit over 1 year ago

What's Changed

Auth Plugins

The auth plugins are installed by default when a new service is created.
In this release, if you choose the uninstall auth plugins after pushing it to Github, the changes will not be reflected in the customizable files (files that are not in the base folder), and you will get the following compilation errors:

image

You need to fix it manually, as follows:

  • Remove imports from files that do not exist, for example: ../auth/gqlDefaultAuth.guard
  • Remove the rolesBuilder from the super() in the constructor (in each entity controller/resolver).

Other Changes

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.2.3...v1.3.0

amplication - v1.2.3

Published by tupe12334 over 1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.2.2...v1.2.3

amplication - v1.2.2

Published by abrl91 almost 2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/1.2.1...v1.2.2

amplication - 1.2.1

Published by abrl91 almost 2 years ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/1.2.0...1.2.1

amplication - 1.2.0

Published by abrl91 almost 2 years ago

What's Changed

New Prisma Module

Significant changes have been made to the generated code regarding Prisma.
Instead of using the package nestjs-prisma we now create our own prisma.module.ts and prisma.service.ts.

@Global()
@Module({
  providers: [PrismaService],
  exports: [PrismaService],
})
export class PrismaModule {}

This module is a global module, meaning that it is decorated with the @Global decorator and we import it only into the main app.module of the generated server. This means that all the entities use the same instance of the Prisma service without importing the Prisma module into the module of each entity.

import { PrismaModule } from "./prisma/prisma.module";

@Module({
  imports: [
   ...,
  PrismaModule,
  ...,
 ]

export class AppModule {}

Breaking Change

This change causes the generated code to fail to build, and manual actions must be taken to resolve it.
You should see the following error after updating the generated code with this version of Amplication:

The reason for the error is that Amplication did not update all the service files with the new code required to use Prisma.
All the service files, [Entity]Service.ts, are owned by you, and Amplication will never override these files directly.
So, you need to manually update these files to support the new code, as following:

New pricing model for the managed service

Amplication has come a long way since its launch as an open-source project on GitHub two years ago. We are a community of thousands of developers now shaping the future of backend development together. :purpleheart:

As we are leveling up with all of the advanced features, robustness, and scale required by enterprises, we remain dedicated to the community, which makes us capable of doing this. ā¤ļø

With the new pricing model, teams working on small projects can continue to use the service at https://app.amplication.com for free. Teams working on larger projects can take advantage of one of the paid plans to enjoy new advanced features and improved use of the Amplication service.

As we launch our paid tiers, we are committed to continuing to support the open-source community. That's why we offer our Pro plan, at no cost, to open-source projects. By doing so, we hope to help these projects succeed and thrive and to continue building a strong and vibrant community of developers around Amplication.

You can read more details about the pricing plan in this blog: https://amplication.com/blog/amplications-pricing-model

Other Changes

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v1.1.2...1.2.0