Skip to content

Validate Customer Email Format (Resolves #55) #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
overcut-ai wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Validate Customer Email Format (Resolves #55) #56

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Changelog

All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]
### Added
- Email format validation for `customer.email` when creating or updating a customer record. Invalid emails now return `400 Bad Request` with message `Invalid email format`. ([#55](https://github.com/overcut-ai/awesome-overcut/issues/55))
2 changes: 2 additions & 0 deletions apps/hotel-management-service-server/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@

This service was generated with Amplication. The server-side of the generated project. This component provides the different backend services - i.e., REST API, GraphQL API, authentication, authorization, logging, data validation and the connection to the database. Additional information about the server component and the architecture around it, can be found on the [documentation](https://docs.amplication.com/guides/getting-started) site.

> **New in this release (unreleased):** The `customer.email` field is now validated for proper email format at both the DTO and API levels. Requests that contain an invalid email (e.g. `"foo"`) will be rejected with a `400 Bad Request` response and the message `"Invalid email format"`. See [issue #55](https://github.com/overcut-ai/awesome-overcut/issues/55) for details.

# Getting started

## Step 1: Configuration
Expand Down
Loading