Skip to content

EDGAR workflow-specific operational change#704

Draft
hermfischer-wf wants to merge 1 commit intoArelle:masterfrom
hermfischer-wf:hf-edgr24.2-upd1
Draft

EDGAR workflow-specific operational change#704
hermfischer-wf wants to merge 1 commit intoArelle:masterfrom
hermfischer-wf:hf-edgr24.2-upd1

Conversation

@hermfischer-wf
Copy link

Reason for change

This change is a companion to EdgarRenderer Pull Request #114

With the Edgar workflow the iXBRLViewer stub is generated twice (for the situation of private and redacted public viewers), not by the usual plugin invocation but instead invoked from an EdgarRenderer iXBRLViewerPluginInterface module.

EdgarRenderer provides unique fact IDs because they're also needed by EDGAR's ixviewer-plus.

It adds a stubOnly flag to generateViewer, so that when saving (into an io.bytes zip) only the stub is saved. The source files are not readable because they may either be encrypted or in a POSTED zip source, but not plain filesystem files. The source files also may not represent the redacted publicly disseminatable files.

Description of change

Add stub-only parameter.

Steps to Test

review:
@Arelle/arelle
@paulwarren-wk

@hermfischer-wf hermfischer-wf requested a review from a team as a code owner July 16, 2024 04:58
@aviary-wf
Copy link

Security Insights

No security relevant content was detected by automated scans.

Action Items

  • Review PR for security impact; comment "security review required" if needed or unsure
  • Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

self.filingDocuments = filingDocuments

def save(self, destination: io.BytesIO | str, zipOutput: bool = False, copyScriptPath: Path | None = None):
def save(self, destination: io.BytesIO | str, zipOutput: bool = False, copyScriptPath: Path | None = None, stubFileOnly: bool = False):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should probably catch stubFileOnly used without useStubViewer and throw an error, as currently you won't get an error, you'll just silently get the first file from the document set.

Perhaps we could move the option on to createViewer and use it to control the calls to addFile? This might be clearer than just only outputting the first file.

@austinmatherne-wk austinmatherne-wk marked this pull request as draft September 30, 2024 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants