REST endpoint a cikin Spring Boot hanya ce (method) a kan wani @RestController, da aka tsara zuwa wani HTTP verb da hanya (path). @RestController = @Controller + @ResponseBody, don haka ana serialize ƙimomin da aka mayar kai tsaye zuwa jikin amsar (JSON ta Jackson) maimakon warware su zuwa wani view.
@RestController
@RequestMapping("/api/users") // base path for every method below
public class UserController {
private final UserService service;
public UserController(UserService service) { this.service = service; }
@GetMapping("/{id}") // GET /api/users/42
public UserDto get(@PathVariable Long id) { // bind {id} from the URL
return service.findById(id); // returned object -> JSON
}
@PostMapping // POST /api/users
@ResponseStatus(HttpStatus.CREATED) // 201 instead of 200
public UserDto create(@Valid @RequestBody UserDto body) { // JSON -> object
return service.create(body);
}
@GetMapping // GET /api/users?role=admin
public List<UserDto> list(@RequestParam(required = false) String role) {
return service.findByRole(role);
}
}
Manyan annotations: @PathVariable yana cire ƙima daga hanyar, @RequestParam yana karanta parameter na query-string, kuma @RequestBody yana deserialize payload ɗin JSON. Ƙara @Valid yana kunna Bean Validation (@NotNull, @Email…) a kan DTO mai shigowa kafin hanyar ka ta gudana.
@GetMapping("/{id}")
public ResponseEntity<UserDto> get(@PathVariable Long id) {
return service.find(id)
.map(ResponseEntity::ok) // 200 + body
.orElse(ResponseEntity.notFound().build()); // 404, no body
}
Wannan aikin backend ne na yau da kullum, don haka masu tambayoyin hira suna tsammanin gwaninta. Ƙarfin amsoshi suna ambaton amfani da DTOs maimakon bayyana JPA entities, tabbatar da shigarwa da @Valid, da mayar da status codes daidai da ResponseEntity — bambanci tsakanin endpoint na wasa da ainihin API.
Ɗakin karatu na tambayoyin hira na IT tare da amsoshi cikakke — daga Junior zuwa Senior.
Ba da Gudummawa