-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve public sharing of Recipes #392
Comments
Thanks for clarifying @christianlupus I do PHP and front-end dev regularly, but have never worked with NextCloud apps. Could you or someone else guesstimate how hard of task this is in terms of learning the APIs? |
Well it is not too hard to enter things. We define the web API ourselves. The nextcloud API is not too complex either. Currently some general preparations should be done in the codebase to help further development. |
I am new to the NextCloud App ecosystem especially Apps in the official |
Although not related with this issue, here are some points:
|
Was looking for a solution to this.... reload in cookbook settings et voila! It's a workaround that works! |
@eddriesen i'm talking public sharing on the web with non-NextCloud users. As for
This is indeed an issue with sharing recipes folders but is unrelated to what I opened this issue about! |
I too would like to be able to publicly share recipes. More than anything else in my NC :) |
Is your feature request related to a problem?
As a NextCloud user, I like being able to publicly share rendered markdown notes from the Notes app like this:
AFAICT as a Cookbook user, when sharing a recipe publicly, there is only the following:
Describe the solution you'd like
Ideally, public sharing of recipes would by default display the same rendering currently displayed to an authenticated user within the Cookbook app- e.g.
Also,it would be helpful to display a pure JSON result by requesting something like
https://cloud.eotl.supply/s/GbHD2MYiWop43ki/json
Describe alternatives you've considered
Unless I completely overlooking something in the app, I don't know of an alternative solution at the moment.
The text was updated successfully, but these errors were encountered: