Sebastian Fey
Sebastian Fey
You’re right, we got a little off track. Still, this specific use case might have (had) an influence on the structure of the file storage, so I guess that’s fine....
These are interesting ideas. The proposal contains two new concepts: 1) An automatic history of any recipe, which is appended with each recipe change. - The history of all recipes...
So for our current requirements, I see most problems solved with the proposed structure. Problems may arise in the future when trying to implement recipe sharing (#120 and discussion above)....
Haven't tested it recently, but since there was no activity here, I'd assume it's not stale
Actually, I’m aiming for 1. _right now_ but for number 2 in the long term. For 2. I infer that there is no problem at all (haven’t tried it yet)....
I leave here as a reference #340, though there is a lot to read. There the support of multiple cookbooks is discussed, which might be an orthogonal concept to collections.
Actually, I think they are already checked. [The responses](https://github.com/nextcloud/cookbook/blob/66efef73dfbad68dd434704d4c56fb1af09432fd/src/components/AppNavi.vue#L145) fall in the 2xx range; the catch statement handles other codes ([compare the axios documentation](https://github.com/axios/axios#handling-errors))
> I feel a bit overwhelmed and also not qualified enough to oversee all things here. Looks like magic to me currently. (Maybe a bit more sleep might help 😉.)...
Not sure if this was introduced with this PR and/or if it's an artifact of my local dev machine but when starting from a clean installation (no recipes) and reload...