Skip to content

Metadata leak in re-frisk #38

Closed
Closed
@stoeckley

Description

Not sure if this should be put here, but re-frisk is possible the culprit for this metadata leak:

day8/re-frame#365 (comment)

Also, note the very large compile time introduced by re-frisk.

Metadata

Assignees

Labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions