I'm not member who contributed to this project.
I'm just new to this celerio-angular-quickstart project and interested in it.
When I tried to make the quickstart run successfully, many issues came out because of incorrect versions I'm using. This project is just out-of-date, and angular is involving too fast.

Here is the correct commands you should use.
Please DO NOT install angular/cli befo

Spring Data JDBC supports one-to-one and one-to-many (either as Set, List or Map) relationships: https://docs.spring.io/spring-data/jdbc/docs/current/reference/html/#jdbc.entity-persistence.types

It would be really useful to also have this feature with R2DBC.

Environment

• Spring boot starter:

  • storage spring boot starter

• OS Type: Windows/Linux/MacOS

• Java version:

  • 1.8

Summary

The ReadMe.md file is not insync with the code. The code contains Upload, download, and list blobs by using the Java Storage SDK V10 version , while the read me contains Java Storage SDK V7

Reproduce steps

Java code & ReadMe.md

Expe

Добавить возможность получить уникальный идентификатор игровой сессии на заданное количество игроков, так чтобы к сессии можно было подключиться только по нему и её проигнорировал обычный матчмейкинг.

Protocol: HTTP
Path: mm/getlink
Method: POST
QueryParam: name&playerCount
Host: {IP}:8080
ResponseBody: gameId

• Наша реализация:
  ![image](https://user-images.githubusercont

The https://github.com/hatunet/spring-data-mybatis-samples appear to be broken with the 2.x release. You no longer have the org.springframework.data.mybatis.annotations.Entity, @OneToMany, etc. and package names have changed.

In Spring Data Moore / Spring Data JPA 2.2 the Specifications type was removed. In DATAJPA-1170 and DATAJPA-1449.

This breaks this library, but it should be rather easy to fix, simply replacing `Specifications

There is a case when entity that describes content is in relation with some other entity and is removed implicitly by cascade and not manually, so it may be necessary to register event listener to unset/delete content described by such entity.

Doing so manually requires boilerplate event listener each one of them injecting ContentStore for particular entity and doing same `store.unsetContent(en