publiccode-editor icon indicating copy to clipboard operation
publiccode-editor copied to clipboard
verified publisher icon italia

V. 2.0.3: No way to remove some validation errors on publiccodeYmlVersion and description.XX.genericName, and Validate successfully

Open itamair opened this issue 10 months ago • 1 comments

Hello, we are still QAing and Testing this new pubbliccode.yml Editor 2.0.x in the same context of European Commission (DIGIT Directorate) and the FOSSEPS Team (https://interoperable-europe.ec.europa.eu/collection/fosseps), and its solid and international adoption for the promotion of open source solutions across EU Public Services.

As followup of this previous issue: https://github.com/italia/publiccode-editor/issues/349 (thanks for all the effort in addressing and fixing most / all those bugs ... )

we are now experiencing the following issue in the actual version 2.0.3:

Problem / Motivation

When an existing pubblicode.yml is uploaded and cannot validate because of the following:

  • publiccodeYmlVersion previous to latest 0.4.0
  • description.XX.genericName DEPRECATED still present

it doesn't Validate also once those error are fixed in the webform / editor.

How to reproduce

  1. Set an ENGLISH interface for the p.yml editor
  2. RESET (Clean) the the p.yml editor
  3. UPLOAD the following publiccode.yml file: "publiccode-opencultura-de.yml" (generated and valid against publiccode.yml standard version "0.2.":

publiccode-opencultura-de.yml.zip

  1. VALIDATE that file The pubbliccode.yml v 2.0.3 stops the Validation with the following errors:

Warnings publiccodeYmIVersion v0.2 is not the latest version, use '0.4.0. Parsing this file as v0.4.0. description.de.genericName This key is DEPRECATED and will be removed in the future Id be the name mo ame and a commer description.en.genericName This key is DEPRECATED and will be removed in the future

Image

  1. The above Validation error/blocker are not removed even if / once those are corrected in the webform / editor, and the Validation will still be blocked by the same ones ...
  2. all stuck!

Could you also reproduce this? if that the case could you properly inspect (if it relates to only those fields or could be a broader application logics issues) and fix?

PS: if the DEPRECATED fields act as blockers they should indeed be better highlighted to the end use (may be with a red font color style, or whatever. In this actual 2.0.3 way the UX on this side is very poor ...

Thanks!

itamair avatar Feb 24 '25 10:02 itamair

hi @itamair . It's on me. I'll check this issues as soon as I can.

valeriocomo avatar Feb 26 '25 10:02 valeriocomo

hi @itamair. this problem is solved by version 2.1.0 but I figure out another problem due to this issue.

valeriocomo avatar Jun 10 '25 13:06 valeriocomo