chore: placeholder filer in the fixtures and docs - #88
Merged
Merged
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
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.
Summary
Uses the placeholder filer in two test fixtures and two documentation lines. This follows the repo's convention for public fixtures and examples:
ACME CORP/ CIK0001234567for an issuer,Doe Janefor a person.Changes
tests/test_efts.pyandtests/test_serve.py: the ownership-form fixtures use the placeholder issuer and reporting owner, with placeholder CIKs and accession.serialize/README.md: a measurement note describes the filings it was measured on without naming them.serve/session.py: a docstring example uses the placeholder's primary-document name.Output Impact
INTERNAL. Tests and documentation only.
Testing
just test-all: 667 passed, 2 skipped; ruff check, ruff format --check and basedpyright clean.