Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide if we want to store additional 'parse_portfolio' metadata #187

Open
bcspragu opened this issue Feb 14, 2024 · 0 comments
Open

Decide if we want to store additional 'parse_portfolio' metadata #187

bcspragu opened this issue Feb 14, 2024 · 0 comments
Labels
cleanup Improve code health without changing UX

Comments

@bcspragu
Copy link
Collaborator

See Grady's comments (1, 2) from #186

General idea is that the updated parser code exposes useful data on both the input (errors, group cols) and output (investor name), and we aren't storing that anywhere yet.

@gbdubs gbdubs added the cleanup Improve code health without changing UX label Feb 16, 2024
@gbdubs gbdubs added this to the MS3 - Public Launch milestone Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Improve code health without changing UX
Projects
None yet
Development

No branches or pull requests

2 participants