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

fix(content-import-job) fix key fields #30843

Conversation

valentinogiardino
Copy link
Contributor

@valentinogiardino valentinogiardino commented Dec 3, 2024

This pull request focuses on updating the content import functionality to use field IDs instead of field names.

Key changes include:

Validation and Schema Updates:

Test Case Adjustments:

  • dotcms-integration/src/test/java/com/dotcms/rest/api/v1/content/dotimport/ContentImportResourceIntegrationTest.java:
    • Added fieldId to store the ID of the first field in the content type. [1] [2]
    • Updated test cases to use fieldId instead of the field name "title". [1] [2] [3] [4]

Postman Collection Update:

  • dotcms-postman/src/main/resources/postman/ContentImportResource.postman_collection.json:
    • Added a script to set the field ID in the collection variables after creating the content type.
    • Updated the fields variable to be empty initially, to be populated by the script.

This PR fixes: #30669

@valentinogiardino valentinogiardino added this pull request to the merge queue Dec 3, 2024
Merged via the queue into main with commit 9a5d196 Dec 4, 2024
36 checks passed
@valentinogiardino valentinogiardino deleted the issue-30669-content-import-job-create-import-job-rest-endpoint-2 branch December 4, 2024 00:01
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.

[Content Import Job Management] Implement the Create Import Job REST endpoint
4 participants