-
Notifications
You must be signed in to change notification settings - Fork 36
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
[Feature] Coordinates-based Cropping #230
Comments
hey @colbyfayock @Baroshem In local after clone and install it looks like this!! |
Hey there @nooras Yes, feel free to grab it! What you see when running the project is ok. It is a playground of all modules features. Feel free to comment the ones that you dont need and work only on the ones related to the issue :) I dont think there are more details or examples here. Colby explained everythin pretty clear :) |
@Baroshem |
What you are refering to is the documentation of the module while running pnpm run dev you are runing the playground. To run the documentation you should type pnpm run docs. But to implement it, first you would need to develop a new functionality and test it in playground and then later on add it to the documentation. |
@nooras Can I do something else to help you get started? |
I am still not able to see in local with pnpm run docs. Its coming like below. Also any docs to refer how to use playground ? |
Could you check what are the errors when running the project? For the second one, there are no docs because playground is just a simple app for testing the module components and composables. You can just add there whatever you want to test :) |
@Baroshem can you please check your discord |
Feature Request
Is your feature request related to a problem? Please describe.
Add support for coordinates-based cropping.
change is available inside of @cloudinary-util/[email protected], should just need to update documentation and add an example as it makes sense.
cloudinary-community/next-cloudinary#509
https://next.cloudinary.dev/cldimage/examples#cropping
The text was updated successfully, but these errors were encountered: