Api#resourceByAssetID does not support same options as in documentation

Aperta
  • Qualcosa non va?
#357 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@adimiz1 ci sta già lavorando.

Dal 6/2/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Bug report for Cloudinary Java SDK

Before proceeding, please update to latest version and test if the issue persists

Describe the bug in a sentence or two.

It seems that Api#resourceByAssetID does not support same parameters as describe in documentation.
In Cloudinary Api Docs . E.g image_metadata is described as supported option. Thus, i would expect that
cloudinary.api().resourceByAssetID(asset.asset_id(), Map.of("image_metadata", true)) would result in GET /v1_1/<client>/resources/<asset-id>?image_metadata=true. But actually it results in /v1_1/<client>/resources/<asset-id> without 'image_metadata' parameter.

Api#resourceByAssetID implementation does not match configuration options in documentation.

    public ApiResponse resourceByAssetID(String assetId, Map options) throws Exception {
        if (options == null) options = ObjectUtils.emptyMap();
        if(options.get("fields") != null) {
            options.put("fields", StringUtils.join(ObjectUtils.asArray(options.get("fields")), ","));
        }
        Map params = ObjectUtils.only(options, "tags", "context", "moderations", "fields");
        ApiResponse response = callApi(HttpMethod.GET, Arrays.asList("resources", assetId), params, options);
        return response;
    }

Since with simple curl the api responds with expected image metadata included my guess is that the java implementation is too restrictive.

Issue Type (Can be multiple)

[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[x ] Behaviour - Functions aren’t working as expected (Such as generate URL)
[ ] Documentation - Inconsistency between the docs and behaviour
[ ] Other (Specify)

Steps to reproduce

… if applicable

Error screenshots or Stack Trace (if applicable)

…

Build System

[ ] Maven
[x ] Gradle
[ ] Other (Specify)

OS (Please specify version)

[ ] Windows
[ ] Linux
[ ] Mac
[ ] Other (specify)

Versions and Libraries (fill in the version numbers)

Cloudinary Java SDK version - 2.0.0
JVM (dev environment) - 0.0.0
JVM (production environment) - 0.0.0
Maven - 0.0.0 / N/A
Gradle - 0.0.0 / N/A

Repository

If possible, please provide a link to a reproducible repository that showcases the problem

Lingua principale
Java
Stelle
176
Fork
113
Merge medio
9g 20h
PR unite (30g)
2

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudinary/cloudinary_java

Tutte le issue di cloudinary/cloudinary_java

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.