Till Prochaska
Till Prochaska
This ticket from 2019 might be related: #878
Hi @MottiniMauro, thanks a lot for your reply! As far as I can see, this should be a small change. Thanks for offering help -- might get back to this...
Hi @MottiniMauro, just wanted to ask if you had a chance to look into the respective PR (#952). No pressure at all, just wanted to make sure this didn’t get...
According to the changelog, there are two breaking changes in this update: **1) Error handling:** This should only affect apps that check for specific error types (e.g. network error vs....
@Rosencrantz Anything specific (regarding to API requests/responses) I should look out for?
I asked @pudo about this to understand the reasoning behind the current implementation and we figured out that it’s a bug. **Current behavior:** If the main entity (e.g. payment in...
@pudo You mentioned that we probably wouldn’t want to link to entities that are not a thing, because they usually only contain little information when expanded. In practice, it seems...
> Most of the desired features described above can be achieved through defining the banner message in a setting and exposing that through metadata endpoint. Wait, do we have global...
> No we don't. I was talking about environment variable settings only. And a setting like that is already there as ALEPH_APP_BANNER in Ah, thanks for clarifying. I might be...
> One further option beyond those that we've already discussed here might be to make use of a microservice for communicating this information. It could exist seperately from Aleph and...