chore: pre-2.0 polish - storage-neutral wording and README gaps - #43
Merged
Conversation
- create-loggable-indexes output no longer says "index" (the storage may be a database table); command name unchanged - README system requirements now list Doctrine ORM 3.4+ and DoctrineBundle, which composer.json has required since 1.2.0 - README warns that maker-generated remove methods null the owning side, which makes LoggableChildInterface::logTo() return null during orphan removal and silently drops the removal log
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Three small gaps left before tagging 2.0.0, all surfaced while validating the storage abstraction (#40) with a relational backend:
locastic:activity-logs:create-loggable-indexesprints "Creating ... activity_log index" even when the aliased storage creates database tablesremove*()methods null the owning side, which makesLoggableChildInterface::logTo()return null during orphan removal, so the removal is silently never logged. This bit the demo app with stock generated codeChanges
Verification