amplication

πŸ”₯πŸ”₯πŸ”₯ The Only Production-Ready AI-Powered Backend Code Generation

OTHER License

Downloads
864
Stars
15.2K
Committers
285
View Code on GitHub Visit Website View on X
Ecosystems: JavaScript, TypeScript, Node.js, .NET, C#, GraphQL, Nest

Bot releases are hidden (Show)

amplication - v0.14.3

Published by arielweinberger over 2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.14.1...v0.14.3

amplication - v0.14.1

Published by arielweinberger over 2 years ago

What's Changed

Fixing minor issues.

fix

hotfix

Full Changelog: https://github.com/amplication/amplication/compare/v0.14.0...v0.14.1

amplication - v0.14.0

Published by souravjain540 over 2 years ago

What's Changed

Amplication is ramping up to be a true enterprise-level solution, and with the release of v0.14.0 we have taken a major step towards this goal. By supporting microservices, we have set the groundwork to enable projects at all scales.

Let's talk about the main changes in this release.

Modular Code Generation πŸ’»

Starting from Amplication 0.14.0 you can separately choose which of the following to generate in your app:

  • REST API
  • GraphQL API
  • Admin UI

Custom directories for the generated components πŸ“–

With Amplication0.14.0, an enhanced directory structure and new parameters enable you to sync multiple apps to a single repository in GitHub.

Amplication 0.14.0 adopts the monorepo strategy, replacing the previous monolithic structure.

This enables Amplication to scale up to large projects and empowers developers to integrate seamlessly with an existing microservice architecture.

Additional benefits include easy code reuse, simplified dependency management, simplified code refactoring and improved cross-team collaboration.

A separate Dockerfile for each component πŸ‘€

In order to boost scalability and maintainability, Amplication now generates two separate Dockerfiles - one for the Server and another one for the Admin UI. Also, we removed all other files that were generated in the root folder, bringing us closer to a true monorepo design.

Removal of Sandbox Deployment ❎

In previous releases, every app created on Amplication Cloud was deployed to a sandbox environment. After listening to our users, we understood that this feature had some limitations and we decided to remove it.

Release 0.14.0 BLOG πŸ’œ

To know every detail about the release of what is changed and how it will impact you to use Amplication, we recommend you to read the detailed blog created by our team by clicking here!

feat

fix

build

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.13.1...v0.14.0

amplication - 0.13.1

Published by souravjain540 over 2 years ago

What's Changed

Code View πŸ‘€

One of the major features we included in 0.13.1 release is Code View.

Now you don't have to go to your GitHub repository again and again after every build to see the changes you have made using Amplication.

You can view the whole code generated by Amplication on our website.

feat

fix

Important information

This change actually impacts only contributors with an existing clone, not new contributors with a new clone, nor users with the generated app.

In release 0.13.1, the database credentials and connection URL have changed. For this reason, if you are an existing user, after pulling release 0.13.1 you must perform the following steps:

  1. To kill old running docker containers:
docker container ls
docker container rm -f [list-of-containers-id]
  1. To clean your existing containers, volumes, and images, run:
docker container prune
docker volume prune
  1. In the root Amplication folder run:
npm run docker:dev

This command will run a new docker container consisting of Kafka and DB.

The following instructions are for all contributors:

Fill the value of the env file, to ensure that the following services function as expected:

  • amplication-server
  • amplication-git-pull-request-service
  • amplication-git-pull-service
  • amplication-storage-gateway
# BASE_BUILDS_FOLDER 
BASE_BUILDS_FOLDER=[path-to-local-folder] //  example:  /Users/myname/tempFolder

To ensure the Kafka client is connected, open localhost:8080 in the browser or click the Open in Browser icon on the Docker desktop.

image

The green dot confirms that the Kafka Broker is connected:

image

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.13.0...v0.13.1

amplication - v0.13.0

Published by souravjain540 over 2 years ago

What's Changed

Licensing Model

To secure the future of Amplication’s application development revolution, and to continue our commitment to the open-source community, we have introduced an updated licensing model. Read more about it here.

feat

fix

build

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.9...v0.13.0

amplication - v0.12.9

Published by souravjain540 over 2 years ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.8...v0.12.9

amplication - v0.12.8

Published by souravjain540 over 2 years ago

What's Changed

fix

feat

docs

build

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.7...v0.12.8

amplication - 0.12.7

Published by yuval-hazaz over 2 years ago

We are happy to announce the new release of Amplication 0.12.7 πŸ₯³

Help us spread the word about Amplication by starring 🌟 the repo or tweeting 🐦 about the release. πŸš€

Amplication release 0.12.7 is a good example of how we keep our code fine-tuned while introducing awesome new features.

We have done code refactoring with significant improvements to the generated code while introducing support for public endpoints - a feature that was requested by many of our enterprise users.

New interceptors for access controls 🌠

We created two new NestJS Interceptors to enforce Access Control policies:

AclValidateRequestInterceptor - this interceptor is used to validate that users are not updating or creating data they are not allowed to, based on the permissions that were defined for their role.

AclFilterResponseInterceptor - this interceptor is used to filter the response data based on the permissions that were defined for their role.

Interceptor refactored code example

Before

When creating a customer record, the request data was checked for any property that is not allowed to be updated by the current user, and an exception is thrown when needed.

The function was not easily readable and included a lot of boilerplate code.

@nestAccessControl.UseRoles({
    resource: "Customer",
    action: "create",
    possession: "any",
  })
  @common.Post()
  async create(
    @common.Body() data: CustomerCreateInput,
    @nestAccessControl.UserRoles() userRoles: string[]
  ): Promise<Customer> {
    const permission = this.rolesBuilder.permission({
      role: userRoles,
      action: "create",
      possession: "any",
      resource: "Customer",
    });
    const invalidAttributes = abacUtil.getInvalidAttributes(permission, data);
    if (invalidAttributes.length) {
      const properties = invalidAttributes
        .map((attribute: string) => JSON.stringify(attribute))
        .join(", ");
      const roles = userRoles
        .map((role: string) => JSON.stringify(role))
        .join(",");
      throw new errors.ForbiddenException(
        `providing the properties: ${properties} on ${"Customer"} creation is forbidden for roles: ${roles}`
      );
    }
    return await this.service.create({
      data: data,
      select: {
        id: true,
        createdAt: true,
        updatedAt: true,
        name: true,
      },
    });
  }

After

Now, the boilerplate code has been removed, and the function includes only a single line of code that calls the service.create function.

Instead of the boilerplate code, the AclValidateRequestInterceptor interceptor was added as a decorator to the function.

@common.UseInterceptors(AclValidateRequestInterceptor)
  @nestAccessControl.UseRoles({
    resource: "Customer",
    action: "create",
    possession: "any",
  })
  @common.Post()
  async create(@common.Body() data: CustomerCreateInput): Promise<Customer> {
    return await this.service.create({
      data: data,
      select: {
        id: true,
        createdAt: true,
        updatedAt: true,
        name: true,
      },
    });
  }

Public Endpoints πŸš€

When building APIs, usually you would like to secure the API so it can be accessed by authorized users only. But, in many use cases, you might be required to build a public API, and sometimes, you may even need to build an API where some endpoints are private while other endpoints are public.

The request to support public endpoints is one of the most popular requests on our GitHub repository #2006.

We have now introduced built-in support to define endpoints as public. This option is available per action per entity- meaning you can easily configure the endpoint so that creating, editing, or deleting blog posts will require authentication, but for viewing the blog posts, no authentication will be needed.

Endpoint Authentication Example

//This endpoint requires authentication
@common.UseInterceptors(AclFilterResponseInterceptor)
@nestAccessControl.UseRoles({
resource: "Customer",
action: "read",
possession: "any",
})
@common.Get()
async findMany(@common.Req() request: Request): Promise<Customer[]> {

//This endpoint is accessible by authenticated and non-authenticated users
//We use the @Public decorator to flag public endpoints
@Public()
@common.Get()
async findMany(@common.Req() request: Request): Promise<Customer[]> {

General πŸ”Ή

Issue Description
Removed unnecessary files in the root of the project.
Creating models without auth guard.

Generated App πŸ“±

Issue Description
Added logic for handling public queries and mutation for resolvers to-many and to-one relations.
Added .server-id to gitignore.
Removed unused parameters from controller endpoints.
Removed unused imports and parameter on controller base and resolver base.
Removed unused imports of interceptors when all the methods on controllers and resolvers are public.
Restructured the place of decorator on the controllers and resolvers.
Changed the methods names on dsg create-controller template to key on option map.

Generated Server πŸ’Ύ

Issue Description
Changed the auto cleanup time period, which happens after deployment, from 30 days to 14 days.
Fixed the bug where public decorator in m2m is added to related entity instead of entity.

CLI πŸ–₯️

Issue Description
Removed unused package @ockuf/test in CLI.

Amplication Client πŸ‘¨β€πŸ’»

Issue Description
Improved the readability of the text in the Amplication client.
Fixed the unnecessary padding dropdown has on Sync with Github screen.
Fixed the wrong spacing and added missing hover effect on Create App screen.

Dependencies ⚠️

Issue Description
Upgraded the root dsg @nestjs/passport version to 8.2.1.

The complete list of all issues resolved in this release can be found on the 0.12.7 milestone on Github

Credits πŸ‘

For this release, we had the help of many contributors – thank you all very much!

  • @jainpawan21 πŸ’―
  • @devblin πŸ’―
  • @abrl91 πŸ’―
  • @achamorro-dev πŸ’―
  • @tupe12334 πŸ’―
  • @souravjain540 πŸ’―

amplication - 0.12.6

Published by yuval-hazaz over 2 years ago

We are happy to announce the new release of Amplication 0.12.6 πŸ₯³

Help us spread the word about Amplication by starring 🌟 the repo or tweeting 🐦 about the release. πŸš€

In this release, we have improved the generated app by including new enhancements like handling the permissions through the validate input interceptor. Community has also made some minor fixed to the Amplication Client.πŸ’œ

Generated App πŸ“±

Validate input interceptor to handle the permissions

We are handling the permissions now in a way that makes the route handlers massive and less readable.
By creating a permissions interceptor, we can handle the permissions stuff outside the function body and manipulate the returned value according to the user's permission right before sending the result to the client.

https://docs.nestjs.com/interceptors

image

Use case

By using a permission interceptor, we would not only achieve cleaner architecture but also could handle public routes in the feature easily.

As a second step, we will implement a validate input interceptor which would be responsible of validate the input of mutations actions such as create, update and delete in REST and Mutation in qraphql.
On the request body of those requests, we have to validate every attribute - if the user with the role that tries for example to update the customer address, has permission not only to mutate the customer but specifically to mutate his address attribute.

Issue Description
Created validate input interceptor to handle the permissions.
Fixed wrong request body on create update and delete m2m nested entity.
Fixed wrong resource on nest access control UseRoles.

Generated Server πŸ’Ύ

Issue Description
Improved the naming of two new interceptors in order to provide more readability and meaning to the name.
Fixed the peer dependencies conflict with error which comes when we try to run setup:dev.

Amplication Client πŸ‘¨β€πŸ’»

Issue Description
Fixed the different structure to a standard structure in all screens of the app.
Fixed the size of search bar on commit screen which was too big and different from other screens.

Dependencies ⚠️

Issue Description
Upgraded the minimist version from 1.2.5 to 1.2.6.

The complete list of all issues resolved in this release can be found on the 0.12.6 milestone on Github

Credits πŸ‘

For this release, we had the help of many contributors – thank you all very much!

  • @molaycule πŸ’―
  • @EugeneTseitlin πŸ’―
  • @germanilia πŸ’―
  • @abrl91 πŸ’―
  • @mshidlov πŸ’―
  • @tupe12334 πŸ’―
  • @yuval-hazaz πŸ’―
  • @souravjain540 πŸ’―

amplication - 0.12.5

Published by souravjain540 over 2 years ago

What's Changed

docs

fix

feat

build

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.4...v0.12.5

amplication - 0.12.4

Published by souravjain540 over 2 years ago

What's Changed

docs

fix

build

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.3...v0.12.4

amplication - 0.12.3

Published by souravjain540 over 2 years ago

What's Changed

fix

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.2...v0.12.3

amplication - 0.12.2

Published by souravjain540 over 2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.1...v0.12.2

amplication - 0.12.1

Published by souravjain540 over 2 years ago

What's Changed

Full Changelog: https://github.com/amplication/amplication/compare/v0.12.0...v0.12.1

amplication - 0.12.0

Published by souravjain540 over 2 years ago

We are happy to announce the minor release of Amplication 0.12.0 πŸ₯³

Help us spread the word about Amplication by starring 🌟 the repo or tweeting 🐦 about the release. πŸš€

In this release, we have made a significant change, migrating from OAuth GitHub integration to GitHub App integration. In addition, we have upgraded the core libraries and done some fixes.πŸ’œ

Major Update ❇️

Migrating from OAuth GitHub integration to GitHub App integration.

We are migrating from OAuth GitHub integration to GitHub App integration. Over the past few months, the community gave us a lot of feedback about managing and controlling the permissions.

GitHub Apps are the officially recommended way to integrate with GitHub because they offer many advantages over a pure OAuth-based integration.

Instead of using the user Auth key, we will use the App ID. For each sync, the app gets its unique identifier, combined with the Amplication App secret key. GitHub grants access to APIs as Amplication and not as the users themselves.

With this change, we will stop using OAuth App integration. This will disconnect all of your connected repositories from Amplication.

To reconnect your repositories, install the Amplication App on your GitHub profile\organization using the Amplication Sync with GitHub App option.

image

Once the app is installed, you can reconnect all of your disconnected repositories, and continue to work as before.

image

Benefits

  • Fine-grained permissions target the specific information a GitHub App can access, allowing the app to be more widely used by people and organizations with security policies than OAuth Apps, which cannot be limited by permissions.

  • Short-lived tokens provide an authentication method that is more secure than OAuth tokens. An OAuth token does not expire until the person who authorized the OAuth App revokes the token. GitHub Apps use tokens that expire quickly, creating a much shorter time for compromised tokens to be in use.

  • Built-in, centralized webhooks receive events for all repositories and organizations that can be accessed by the app. Conversely, OAuth Apps require a webhook to be configured for each repository and organization accessible to the user.

  • Bot accounts don't consume a GitHub seat and remain installed even when the person who initially installed the app leaves the organization.

Amplication Server πŸ’Ύ

Issue Description
Migrated from OAuth GitHub integration to GitHub App integration.
Deleted entities are now disabled. To make people understand what happened, we added a tiny tooltip explaining why it's disabled.

Amplication Client πŸ‘¨β€πŸ’»

Issue Description
Updated the icon pack.

The complete list of all issues resolved in this release can be found on the 0.12.0 milestone on Github

Credits πŸ‘

For this release, we had the help of many contributors – thank you all very much!

  • @morhagbi πŸ’―
  • @tupe12334 πŸ’―
  • @mshidlov πŸ’―
  • @yuval-hazaz πŸ’―
  • @muhsinkamil πŸ’―
  • @souravjain540 πŸ’―

amplication - 0.11.4

Published by souravjain540 over 2 years ago

We are happy to announce the patch release of Amplication 0.11.4 πŸ₯³

Help us spread the word about Amplication by starring 🌟 the repo or tweeting 🐦 about the release. πŸš€

In this release, we have improved the generated app by including new enhancements, such as many-to-many relationships and filtering an entity list by relation. In addition, we have upgraded the core libraries and done some fixes.πŸ’œ

Generated App πŸ“±

Connect and disconnect records with a many-to-many relationships

In previous versions, there was no way to link entities that used a many-to-many relationships. Now you can connect and disconnect related entities with many-to-many relationships.

Add connected records

The following example creates a new post and connect three tag records to it.
Any previously linked record will remain linked to the post, even if it was not specified in the connect property

mutation{
  createPost(
    data:{
      title:"Intro to GraphQL API"
      tags:{
        connect:[
          {id:"ckza5hdoh026201s6xdov9997"}
          {id:"ckz9sbil5019501s6piaydpgv"}
          {id:"ckza5hmvm033601s6c3ns25cs"}
        ]
      }
    }
  ){
    id
    title
    tags{
      id
      name
    }
  }
}

Remove connected records

The following example updates a post and disconnect a couple of tags from the post.
Any existing related entity that was not specified in the disconnect property will remain linked to the post.

mutation{
  updatePost(
    where:{
    	id:"ckzi8urcd119501s6nbx8au6y"
  	}
    data:{
      tags:{
        disconnect:[
          {id:"ckz9sbil5019501s6piaydpgv"}
          {id:"ckza5hmvm033601s6c3ns25cs"}
        ]
      }
    }
  ){
    id
    title
    tags{
      id
      name
    }
  }
}

Set the list of connected records

The following example updates a post and set the list of connected tags.
Any previously linked record that was not specified in the set property will be removed.

mutation{
  updatePost(
    data:{
      tags:{
        set:[
          {id:"ckza5hdoh026201s6xdov9997"}
          {id:"ckz9sbil5019501s6piaydpgv"}
        ]
      }
    }
  ){
    id
    title
    tags{
      id
      name
    }
  }
}

Filter an entity by a related record

Added the ability to filter an entity by values on a related record.

The following example returns all posts that are connected to a tag with a name equal to "open-source".

query{
  posts(
    where:{
      tags:{
        some:{
          name:{
            equals:"open-source"
          }
        }
      }
    }
  )
  {
    id
    title
  }
}
Issue Description
Now GraphQL API allows the creation of data with many-to-many relationships.
Fixed the generated app so it uses the correct data type for many-to-many relationships on the REST API controller.
The decorator gqlUserRoles.decorator.ts now checks for the existence of the user on the request and fails when there is no user in context.
Started using multi-line comments for a clear and readable generated code message.
Added the ability to filter an entity by relation.
Added support for creation of many-to-many relationships.

Amplication Client πŸ‘¨β€πŸ’»

Issue Description
Fixed the bug where the tooltip text is not visible in light theme mode.
Now, on clicking the profile button, the user is taken to a profile page.

Dependencies ⚠️

Issue Description
Upgraded the node-fetch version from 2.6.6 to 2.6.7.
Upgraded the node_modules/node-fetch version from 2.6.6 to 2.6.7.
Upgraded the ra-data-graphql-amplication version from 0.0.6 to 0.0.8.

The complete list of all issues resolved in this release can be found on the 0.11.4 milestone on Github

Credits πŸ‘

For this release, we had the help of many contributors – thank you all very much!

  • @molaycule πŸ’―
  • @abrl91
  • @mshidlov πŸ’―
  • @tupe12334 πŸ’―
  • @yuval-hazaz πŸ’―
  • @souravjain540 πŸ’―

amplication - 0.11.3

Published by souravjain540 over 2 years ago

We are happy to announce the patch release of Amplication 0.11.3 πŸ₯³

Help us spread the word about Amplication by starring 🌟 the repo or tweeting 🐦 about the release. πŸš€

In this release, we upgrade the core libraries and tools to the latest stable releases, along with other fixes and additions. πŸ’œ

General πŸ“‘

Issue Description
Fixed the bug in which CI failed on 'build': Property getMetadata does not exist on type typeof Reflect.

Amplication Server πŸ’Ύ

Issue Description
Graphql playground loading issue is resolved.
Entity naming restriction was updated to solve generated app migration failing issue due to usage of reserved names in entity naming.
Added Commit/Rebuild Collapse button.
Upgraded the @types/downloadjs version from 1.4.2 to 1.4.3.
Upgraded the node-fetch version from 2.6.1 to 2.6.6.
Upgraded the get-port version from 5.1.1 to 6.0.0.
Upgraded the @octokit/rest version from 18.6.7 to 18.12.0 .
Upgraded the rollup version from 2.53.2 to 2.63.0 .
Upgraded the get-stream version from 6.0.0 to 6.1.1 .
Upgraded the pluralize version from 7.0.0 to 8.0.0 .
Upgraded the @types/lodash version from 4.14.171 to 4.14.178.
Upgraded the fast-glob version from 3.2.7 to 3.2.10.
Upgraded the @google-cloud/secret-manager version from 3.8.1 to 3.10.1.
Upgraded the semver version from 6.3.0 to 7.3.5.
Upgraded the @google-cloud/storage version from 5.3.0 to 5.17.0.
Upgraded the @types/amplitude-js version from 5.11.2 to 5.11.3.
Upgraded the tsconfig-paths version from 3.10.1 to 3.12.0.
Upgraded the query-string version from 4.3.4 to 7.1.1.

Generated App πŸ“±

Issue Description
Added User object to the request in REST API endpoints.
A bug in nestjs/swagger generated the swagger UI in an incorrect way, causing the API request to fail nestjs/swagger#1803. To fix this issue, a new decorator (@ApiNestedQuery) was created to generate the nested properties of the query type as expected.
Added missing support for pagination in REST API controllers, on multiple relation endpoints /api/entities/{id}/sub-entities.

CLI πŸ’»

Issue Description
Upgraded the graphql code gen version from 1.21.8 to 2.3.0.

The complete list of all issues resolved in this release can be found on the 0.11.3 milestone on Github

Credits πŸ‘

For this release, we had the help of many contributors – thank you all very much!

  • @narayand16 πŸ’―
  • @abrl91 πŸ’―
  • @muhsinkamil πŸ’―
  • @0xsapphir3 πŸ’―
  • @noyjs πŸ’―
  • @mshidlov πŸ’―
  • @tupe12334 πŸ’―
  • @yuval-hazaz πŸ’―
  • @souravjain540 πŸ’―

amplication - 0.11.2

Published by souravjain540 over 2 years ago

We are happy to announce the patch release of Amplication 0.11.2. πŸ₯³

Help us spread the word about Amplication by starring 🌟 the repo or tweeting 🐦 about the release. πŸš€

In this release, we upgrade the core libraries and tools to the latest stable releases, along with other fixes and additions. πŸ’œ

Better User Experience ✴️

We take community feedback very seriously and it's always our first priority!

We got some feedback about the user experience and the UI flow of the Commit/Rebuild process.

Previously, the Commit/Rebuild option was on on left of the screen causing an inconistent UI experience. To improve the flow we shifted it to the right of the screen. The UI flow is now more consistent. πŸ˜‰

We have also added a skeleton loading animation on the bottom bar whenever the user launches the Commit/Rebuild function. πŸŽ‰

image

General πŸ“‘

Issue Description
Added Cache to the setup script GitHub dev action.
Updated the default react icon with amplication icon.
The new issue templates were updated and made more accessible.
A new PR template, with PR guidelines, was added for welcoming and helping contributors on their way to contribute changes.

Amplication Server πŸ’Ύ

Issue Description
Improved the UX when app gives error message when trying to login with a user that doesn't exist .
Fixed the bug where there is no warning displayed when we want to create a new app but with the name of another app.
New dedicated @amplication/server Dockerfile.
Added a dedicated docker file to @amplication/client .
Moved commit button from the bottom to the right of the screen.
Dependency lodash updated from version 4.17.20 to version 4.17.21
Upgraded version of react-scripts from 3.4.4 to 5.0.0.
Removed @rmwc library completely and replaced it with @mui/material.
Upgraded react version from 16.13.1 to17.0.2.
Upgraded react-dom version from 16.13.1 to17.0.2.
Upgraded styled-components version from 5.1.1 to5.3.3.
We have upgraded @typescript-eslint/eslint-plugin version from 4.28.3 to5.9.1.
Upgraded @typescript-eslint/parser version from 4.28.3 to5.9.1.
Upgraded eslint version from 7.17.0 to8.6.0.
Upgraded eslint-config-react-app version from 6.0.0 to7.0.0.
Upgraded eslint-plugin-import version from 2.23.4 to2.25.4.
Upgraded eslint-plugin-jsx-a11y version from 6.4.1 to6.5.1.
Upgraded eslint-plugin-react version from 7.24.0 to7.28.0.
Upgraded eslint-plugin-react-hooks version from 4.2.0 to4.3.0.
Removed the storybook library temporarily to avoid the conflicts.
Removed the react-device-detect version 1.14.0.
Upgraded react-select version from 3.1.1 to5.2.1.
Added @types/classnames version 2.3.1.
Removed @types/react-select version 3.0.27.

Amplication App πŸ“±

Issue Description
Added comment to all files in entities base folder to tell developer to not to change code manually, it'll be overwritten.

CLI πŸ’»

Issue Description
Fixed conflicting option in the Amplication's CLI (entities:fields:update).

The complete list of all issues resolved in this release can be found on the 0.11.2 milestone on Github

Credits πŸ‘

For this release, we had the help of many contributors – thank you all very much!

  • @mshidlov πŸ’―
  • @tupe12334 πŸ’―
  • @0xsapphir3 πŸ’―
  • @Rutam21 πŸ’―
  • @abrl91 πŸ’―
  • @yuvalhazaz πŸ’―
  • @noyjs πŸ’―
  • @souravjain540 πŸ’―

amplication - 0.11.1

Published by mshidlov almost 3 years ago

We are happy to announce of a new Amplication patch release version 0.11.1. πŸ₯³

In this release, we upgraded many of the libraries that help us create Amplication. In addition, we are releasing collaboration improvement merged with the help of our community (@g-traub). πŸ’œ

The main Highlights of this release are πŸ‘‡

General πŸ“‘

Issue Description
New workflow on pull requests for testing generated app
Dependency winston updated from version 3.3.3 to version 3.3.4 cross Amplication project.

Amplication Server πŸ“‘

Issue Description
Changing an element on shared workspace, makes the element to become locked for changes by other users until the changes are committed. Now changed elements can be unlocked when their changes are reverted by the user.
Dependency class-transformer updated from version 0.3.1 to version 0.5.1
Dependency passport updated from version 0.4.1 to version 0.5.2
Dependency @nestjs/graphql updated from version 7.9.1 to version 7.11.0
Dependency tar-fs updated from version 2.1.0 to version 2.1.1 and dependency@types/tar-fs updated from version 2.0.0 to version 2.0.1
Dependency @types/tar-stream updated from version 2.2.1 to version 2.2.2
Dependency adm-zip updated from version 0.5.5 to version 0.5.9
Dependency sleep-promise updated from version 8.0.1 to version 9.1.0
Dependency @types/passport-github updated from version 1.1.6 to version 1.1.7
Dependency validate-color updated from version 2.1.1 to version 2.2.1
Dependency bcrypt updated from version 5.0.0 to version 5.0.1
Dependency recast updated from version 0.20.4 to version 0.20.5
Dependency class-validator updated from version 0.12.2 to version 0.13.2
Dependency json-schema-to-typescript updated from version 10.1.4 to version 10.1.5
Dependency docker-compose updated from version 0.23.12 to version 0.23.14
Dependency @types/cron updated from version 1.7.2 to version 1.7.3
Dependency cronstrue updated from version 1.105.0 to version1.122.0
Tests to verify json fields creation, testing that json field is created with the proper types corect types, JsonValue for entity dto and InputJsonValue for inputs dtos

Generated App πŸ“‘

Issue Description
Camel case naming entities relation parsing error in the generated admin UI
Dependency @amplication/design-system removed.
Dependency class-transformer updated from version 0.3.1 to version 0.5.1
Dependency passport updated from version 0.4.1 to version 0.5.2
Dependency @nestjs/graphql updated from version 7.9.1 to version 7.11.0
Dependency swagger-ui-express updated from version 4.1.6 to version 4.3.0
Dependency nest-access-control updated from version 2.0.2 to version 2.0.3
Dependency @types/rc updated from version 1.1.0 to version 1.2.0
Dependency class-validator updated from version 0.12.2 to version 0.13.2

CLI πŸ“‘

Issue Description
Dependency @types/url-join updated from version 4.0.0 to version 4.0.1
Dependency @oclif/test updated from version 1.2.8 to version 1.2.9

The complete list of all issues resolved in this release can be found on the 0.11.1 milestone on Github

Credits πŸ‘

For this release, we had the help of 4 contributors – thank you all very much!

  • @mshidlov πŸ’―
  • @tupe12334 πŸ’―
  • @g-traub πŸ’―
  • @mikenussbaumer πŸ’―

amplication - 0.11.0

Published by souravjain540 almost 3 years ago

We are happy to announce the minor release of Amplication 0.11.0. πŸ₯³

In this release, we upgrade the core libraries and tools to the latest stable releases, along with other fixes and additions. πŸ’œ

The main Highlights of this release are πŸ‘‡

General πŸ“‘

Issue Description
Node version is updated from 14.0.0 to the 16.13.1(LTS), now Amplication will support both versions.
NPM version is updated from 7.3.0 to 8.1.2, now Amplication will support both versions.
Issues templates are improved for contributors when they open new issues, including automation to help maintainers to address issues from the community.
Lerna is updated from 3.22.1 to version 4.0.0.

Amplication Server πŸ’Ύ

Issue Description
Improved a typo in naming convention of .prettierignore from .pretttierignore .
Fixed error that parses the relations incorrectly when using camel case entities relation.
Added two missing packages @google-cloud/storage and @octokit/oauth-authorization-url in package.json file.
Updated prisma version from 2.19.0 to 3.6.0, preparing for the next prisma update(3.7.0) that will work on M1 architecture.
NestJs is updated from 7.6.18 to 8.2.3.

Generated App πŸ’»

Issue Description
Package name in package.json updated to package naming best practice.
Updated prisma version from 2.19.0 to 3.6.0, preparing for the next prisma update(3.7.0) that will work on M1 architecture.
NestJs is updated from 7.6.18 to 8.2.3.

The complete list of all issues resolved in this release can be found on the 0.11.0 milestone on Github

Credits πŸ‘

For this release, we had the help of 6 committers – thank you all very much!

  • @mshidlov πŸ’―
  • @tupe12334 πŸ’―
  • @yuval-hazaz πŸ’―
  • @AsianCat54x πŸ’―
  • @souravjain540 πŸ’―
  • @joebowbeer πŸ’―

Package Rankings
Top 9.55% on Proxy.golang.org
Top 3.05% on Npmjs.org
Related Projects
amplify-cli

The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.

23 Aug 2018 2,810
example-storefront

Example Storefront is Reaction Commerce’s headless ecommerce storefront - Next.js, GraphQL, React...

03 Apr 2018 604
reaction

Mailchimp Open Commerce is an API-first, headless commerce platform built using Node.js, React, G...

18 Sep 2013 12,321