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

REL-1198: List value URI definition should work with neo4j RDF storage. #3908

Merged
merged 4 commits into from
Oct 23, 2023

Conversation

vbyndych
Copy link
Contributor

Goal

List value URIs can be modified via user interface. Yet implementation is modifying SQL statements table directly, and would not work with neo4j RDF storage.

Changelog

  • feat: updated list find/persist functionality to use complex search functionality to fetch lists data.

How to test / use

Lists are used in many places but the easiest way to test them is lists settings page.

  1. Login to TAO Authoring / Studio
  2. Open /tao/Main/index?structure=settings&ext=tao&section=taoBo_list
  3. Try to create/update/delete lists and lists values.

Dependencies

Copy link
Contributor

@yaraslau-kavaliou yaraslau-kavaliou left a comment

Choose a reason for hiding this comment

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

Looks good!

Copy link
Contributor

@yaraslau-kavaliou yaraslau-kavaliou left a comment

Choose a reason for hiding this comment

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

Looks good!

Base automatically changed from feat/REL-1197/rdf-import-export-neo4j to develop October 20, 2023 14:43
@augustas augustas closed this Oct 20, 2023
@augustas augustas reopened this Oct 20, 2023
Copy link
Contributor

@augustas augustas left a comment

Choose a reason for hiding this comment

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

Working well for me. Just need to update dependency to generis

  • 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
  • Changelog is updated according to changes (if applicable)
  • Documentation is updated according to changes (if applicable)

@codecov-commenter
Copy link

codecov-commenter commented Oct 23, 2023

Codecov Report

Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (ed38ea6) 27.55% compared to head (a4b7d8b) 27.36%.
Report is 37 commits behind head on develop.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #3908      +/-   ##
=============================================
- Coverage      27.55%   27.36%   -0.20%     
+ Complexity     10976    10968       -8     
=============================================
  Files            922      922              
  Lines          33910    33810     -100     
=============================================
- Hits            9345     9251      -94     
+ Misses         24565    24559       -6     
Files Coverage Δ
models/classes/Lists/Business/Domain/Value.php 87.80% <100.00%> (ø)
...s/Business/Domain/ValueCollectionSearchRequest.php 87.67% <100.00%> (+2.94%) ⬆️
...Access/Repository/RdfValueCollectionRepository.php 82.90% <91.80%> (-6.09%) ⬇️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions
Copy link

Version

Target Version 53.11.0
Last version 53.10.0

There are 0 BREAKING CHANGE, 1 feature, 1 fix

@vbyndych vbyndych merged commit bf432c6 into develop Oct 23, 2023
4 of 5 checks passed
@vbyndych vbyndych deleted the feat/REL-1198/list-neo4j branch October 23, 2023 16:16
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.

4 participants