Remo

Results 26 issues of Remo

**Description of the issue**: jib, jibBuildTar and jibDockerBuild are all standalone tasks doing both the building and publishing. Expectation would rather be that those three tasks share a common tasks...

area/jib-maven-plugin
area/jib-core
area/jib-gradle-plugin
area/jib-cli
type:bug
priority: p4

see https://stackoverflow.com/questions/8139437/how-to-set-the-column-order-of-a-composite-primary-key-using-jpa-hibernate, crnk should support this behavior as well as default to prevent a index mismatch when sorting after a multi-column primary key.

for plainjson format, this is already working. Should support the same for pure JSON:API,

Details can be found here: http://www.crnk.io/releases/stable/documentation/#_properties. For historic reasons it was BY_TYPE. But BY_ROOT_PATH should be more apprioriate for most use cases.

orignally from @ckarthik17 Currently, ExceptionMapperRegistryBuilder always adds CrnkExceptionMapper as a default exception mapper for crnk client. So, even when I try to add an exception mapper by overriding getExceptionMapperRegistry(), always...

many of the current selectors in NgrxJsonApiSelectors could be pure functions. There is no need to wrap those in a service (because the store location is constant since ngrx4).

running two requests in parallel leads to cancellation of first request.

a temporary ID is needed for ngrx-json-api till the POST completes. Adding a new flag "hasTemporaryId" to remove the ID from the POST request again. After that it is up...

to do automatic memory management. Potentially the compact operation should be optimized towards that and may terminate quickly by checking first in the area the query was operating (type, results,...)

e.g. QueryRefreshAction currently refreshes any query from the server regardless whether it was originally a in-memory or remote query. There should be a check for that. Potentially more actions need...