Expand embed_as documentation with usage examples #29
Conversation
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
This aims to clarify the confusion about using embed_as within modules and classes, particularly around when to use the `self.` prefix. The previous documentation briefly mentioned `self.` but did not explain the underlying behavior: the macro generates instance methods by default, and prepending self. creates class methods instead. Added three progressive examples covering top-level usage, module/class usage with self., and an abstract interface pattern for applications needing multiple database classes with shared migration logic (from my example in the reported issue) Closes #15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This aims to clarify the confusion about using embed_as within modules and classes, particularly around when to use the
self.prefix.The previous documentation briefly mentioned
self.but did not explain the underlying behavior: the macro generates instance methods by default, and prepending self. creates class methods instead.Added three progressive examples covering top-level usage, module/class usage with self., and an abstract interface pattern for applications needing multiple database classes with shared migration logic (from my example in the reported issue)
Closes #15