-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
Migrated instrument locations to Dexterity #1705
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
3ef4611
Migrated instrument locations to Dexterity
ramonski b776c3b
Changelog
ramonski 2f9ea0b
Removed PDB
ramonski 6585cc1
Fixed icon
ramonski 716c2cb
Added description
ramonski 5763cd8
Set attributes explicitly
ramonski 129f194
wrapped description into message factory
ramonski 299a35c
Removed unused attribute
ramonski a21023b
Fixed create API for dexterity types
ramonski 139fe22
Improved migration step in upgrade handler
ramonski 2dc181e
Added referenceably behavior to container type as well
ramonski 0cc5a06
Copy snapshots for the container as well
ramonski bea10cd
Merge branch '2.x' into convert-storagelocations-to-dexterity
ramonski e22cc3f
Added link to PR to upgrade step
ramonski 5b3201b
Merge branch 'convert-storagelocations-to-dexterity' of git://github.…
ramonski bda4973
Update the schema fields explicitly
ramonski 83655a8
Call edit after processForm
ramonski 957c9dd
Fixed test
ramonski 3b16e69
Fixed typo
ramonski a812847
Refactored listing view
ramonski File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
57 changes: 0 additions & 57 deletions
57
src/bika/lims/profiles/default/types/InstrumentLocation.xml
This file was deleted.
Oops, something went wrong.
29 changes: 0 additions & 29 deletions
29
src/bika/lims/profiles/default/types/InstrumentLocations.xml
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't be necessary to notify the modification explicitly?
I recall there are some subscribers for
ObjectModifiedEvent
(forContact
,Batch
, ...)Probably for both ATs and DX.
Also, what if we do a
noLongerProvides(IAuditLog, obj)
before the edit and analsoProvides(IAuditLog, obj)
afterwards?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion this modification event was always wrong in that function, because we are creating an object and not modifying it. Therefore, I think it is better to handle that internally as just one transaction.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Understand, however, we'll need to keep this in mind. I think
Batch
type is the only one that might be affected by this change in core, but not sure atm about the scope of this change in other add-ons (e.g. jsonapi)