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

feat: export test with related properties/metadata #2452

Conversation

bartlomiejmarszal
Copy link
Contributor

@bartlomiejmarszal bartlomiejmarszal commented Apr 9, 2024

When exporting test we will export also all resources metadata descriptions as metaMetadata objects in lom notation*

Steps to test

  1. Enable feature flag FEATURE_FLAG_LOM_ONTOLOGY_EXTRACTION
  2. Add properties in items
  3. Add properties in test
  4. Add items with properties in test
  5. Export test
  6. Open and extract zip package
  7. Preview imsmanifest.xml file.
    • Ensure all properties are in place
    • Ensure no duplicates are present
    • Ensure xml file is valid

Copy link

github-actions bot commented Apr 9, 2024

Front-end summary Node 18

💯 Total ✅ Passed ⏭️ Skipped ❌ Failed
708 708 0 0

Copy link
Contributor

@Karol-Stelmaczonek Karol-Stelmaczonek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • New code is covered by tests (if applicable)
  • Tests are running successfully (old and new ones) on my local machine (if applicable)
  • New code is respecting code style rules
  • New code is respecting best practices
  • New code is not subject to concurrency issues (if applicable)
  • Feature is working correctly on my local machine (if applicable)
  • Acceptance criteria are respected
  • Pull request title and description are meaningful

Copy link
Contributor

@tikhanovichA tikhanovichA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job

  • New code is covered by tests (if applicable)
  • Tests are running successfully (old and new ones) on my local machine (if applicable)
  • New code respects code style rules
  • New code respects best practices
  • Feature is working correctly on my local machine (if applicable)
  • Acceptance criteria are respected
  • Pull request title and description are meaningful
  • Pull request's target is not master
  • Commits are following conventional commits
  • Commits messages are meaningful
  • Commits are atomic

Copy link
Contributor

@Karol-Stelmaczonek Karol-Stelmaczonek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • New code is covered by tests (if applicable)
  • Tests are running successfully (old and new ones) on my local machine (if applicable)
  • New code is respecting code style rules
  • New code is respecting best practices
  • New code is not subject to concurrency issues (if applicable)
  • Feature is working correctly on my local machine (if applicable)
  • Acceptance criteria are respected
  • Pull request title and description are meaningful

Copy link

Version

Target Version 48.4.0
Last version 48.3.5

There are 0 BREAKING CHANGE, 8 features, 0 fix

}
asort($labels);
$checksum = implode('', $labels);
common_Logger::e(sprintf('ChecksumGenerator resource before sha1 : "%s"', $checksum));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

55 | ERROR | [x] Expected 1 space after comma in argument list; 2 found

@bartlomiejmarszal
Copy link
Contributor Author

This code will be merged with: #2454

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.

3 participants