Merge branch 'master' of https://git.zipcode.rocks/Cohort4.2/SpringQuickPoll

README.md

@@ -140,7 +140,7 @@ public ResponseEntity<Iterable<Poll>> getAllPolls() {
 * Launch the [Postman](https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop?hl=en) app and enter the URI `http://localhost:8080/polls` and hit Send.
 * Because we don’t have any polls created yet, this command should result in an empty collection.
 * If your application cannot run because something is occupying a port, use this command with the respective port number specified:
-	* ``kill -kill `lsof -t -i tcp:8080` ``
+	* ``npx kill-port 8080``
 
 
 
@@ -506,7 +506,7 @@ public ResponseEntity<?> handleResourceNotFoundException(ResourceNotFoundExcepti
 
 
 
-## Part 5.4 - Validating domain entities
+## Part 5.5 - Validating domain entities
 
 Now it's time to make sure that all objects persisted to the database actually contain valid values. Use the `org.hibernate.validator.constraints.NotEmpty` and `javax.validation.constraints.Size` and `javax.validation.Valid` annotations for validation.
 
@@ -515,7 +515,7 @@ Now it's time to make sure that all objects persisted to the database actually c
   - `question` should be `@NotEmpty`
 - To enforce these validations, add `@Valid` annotations to Poll objects in `RequestMapping`-annotated controller methods (there should be 2)
 
-## Part 5.5 - Customizing validation errors
+## Part 5.6 - Customizing validation errors
 
 In order to customize validation errors we'll need a class for error information. Create a `ValidationError` class in `io.zipcoder.tc_spring_poll_application.dto.error` with the following fields and appropriate getters and setters:
 
@@ -525,14 +525,14 @@ In order to customize validation errors we'll need a class for error information
 We also need a new field in the `ErrorDetail` class to hold errors. There may be multiple validation errors associated with a request, sometimes more than one of the same type, so this field will be a collection, specifically a `Map<String, List<ValidationError>> errors` field.
 
 
-## Part 5.6 - Create a validation error handler
+## Part 5.7 - Create a validation error handler
 
 - add below handler to `RestExceptionHandler`
 
 ```java
 @ExceptionHandler(MethodArgumentNotValidException.class)
 public ResponseEntity<?>
-handleValidationError(  MethodArgumentNotValidException manve,
+handleValidationError(MethodArgumentNotValidException manve,
 						HttpServletRequest request){...}
 ```
 
@@ -559,7 +559,10 @@ for(FieldError fe : fieldErrors) {
 }
 ```
 
-## Part 5.7 - Externalize strings in a messages.properties file
+- Use an autowired `MessageSource` object in the `RestExceptionHandler` to set the message on ValidationError objects (ie: `setMessage(messageSource.getMessage(fe,null));` )
+  - This object will be autowired (or injected) the same way your `CRUDRepository` instances are.
+
+## Part 5.8 - Externalize strings in a messages.properties file
 
 Commonly used strings in your Java program can be removed from the source code and placed in a separate file. This is called externalizing, and is useful for allowing changes to text displayed without impacting actual program logic. One example of where this is done is in internationalization, the practice of providing multilingual support in an application, allowing users to use an application in their native language.
 
@@ -568,8 +571,7 @@ There are two steps needed here to externalize and standardize the validation er
 - Create a `messages.properties` file in the `src/main/resources` directory with the given properties below
   - `messages.properties` is a key-value file stored in plain text. Your IDE may have a table-based view or show the contents as text
   - `.properties` files are a common idiom in Java applications; they contain additional information the application uses that doesn't impact the actual source code.
-- Use an autowired `MessageSource` object in the `RestExceptionHandler` to set the message on ValidationError objects (ie: `setMessage(messageSource.getMessage(fe,null));` )
-  - This object will be autowired (or injected) the same way your `CRUDRepository` instances are.
+
 
 **`messages.properties` content**:
 
@@ -646,6 +648,7 @@ Size.poll.options=Options must be greater than {2} and less than {1}
 ## Part 6.2 - Spring's Built-in Pagination
 
 * Make use of Spring's built-in page number pagination support by researching `org.springframework.data.repository.PagingAndSortingRepository`.
-* Modify respective `Controller` methods to handle `Pageable` arguments.
+* Modify respective `Controller` methods to handle `Pageable` arguments and `Page<T>` return-types.
+* Modify respective `Repository` methods to handle `Page<T>` objects.
 * Send a `GET` request to `http://localhost:8080/polls?page=0&size=2` via Postman.
 * Ensure the response is a `JSON` object with pagination-specific information.