Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
caosdb-pylib
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
caosdb
Software
caosdb-pylib
Commits
929081bc
Commit
929081bc
authored
1 month ago
by
Henrik tom Wörden
Browse files
Options
Downloads
Patches
Plain Diff
DOCS: correct CL statement
parent
6a2c5300
Branches
f-compare
No related tags found
1 merge request
!182
Draft: FIX: do not replace prop during merge
Pipeline
#62422
passed
1 month ago
Stage: code_style
Stage: linting
Stage: test
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGELOG.md
+2
-2
2 additions, 2 deletions
CHANGELOG.md
with
2 additions
and
2 deletions
CHANGELOG.md
+
2
−
2
View file @
929081bc
...
...
@@ -11,8 +11,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
-
convenience functions
`value_matches_versionid`
,
`get_id_from_versionid`
and
`get_versionid`
### Changed ###
-
`
compar
e_entities`
is
now case insensitive with respect to property and
reco
rdtyp
e
n
ame
s
-
`
merg
e_entities`
is
does no longer replace properties in the first entity with the ones of the
second if they a
re
co
nsidered th
e
s
ame
due to the same ID (
`merge_id_with_resolved_entity`
)
### Deprecated ###
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment