Skip to content
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

Edit Metadata API endpoint - support empty values #11273

Draft
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

GPortas
Copy link
Contributor

@GPortas GPortas commented Feb 19, 2025

What this PR does / why we need it:

Which issue(s) this PR closes:

Special notes for your reviewer:

Suggestions on how to test this:

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

This comment has been minimized.

This comment has been minimized.

1 similar comment

This comment has been minimized.

@GPortas GPortas force-pushed the 11243-editmetadata-api-empty-values branch from 86da8d6 to 77f94d0 Compare February 19, 2025 14:04

This comment has been minimized.

…d dataset field types in DatasetFieldValidator

This comment has been minimized.

@coveralls
Copy link

Coverage Status

coverage: 22.765% (+0.03%) from 22.736%
when pulling ac02c79 on 11243-editmetadata-api-empty-values
into 2210d16 on develop.

This comment has been minimized.

1 similar comment
Copy link

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:11243-editmetadata-api-empty-values
ghcr.io/gdcc/configbaker:11243-editmetadata-api-empty-values

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Edit Metadata API endpoint - not allowing empty values
2 participants