Api#resourceByAssetID does not support same options as in documentation

Ouverte
  • Quelque chose ne va pas ?
#357 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@adimiz1 y travaille déjà.

Depuis le 6/2/2025.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

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

Langage dominant
Java
Étoiles
176
Forks
113
Merge moyen
9 j 20 h
PR mergées (30 j)
2

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de cloudinary/cloudinary_java

Toutes les issues de cloudinary/cloudinary_java

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.