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.

Sign up for GitHub

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

Jump to bottom

Consider if/how we should track RawInput #2419

Open
KathleenDollard opened this issue May 5, 2024 · 1 comment
Open

Consider if/how we should track RawInput #2419

KathleenDollard opened this issue May 5, 2024 · 1 comment
Labels
Design Powderhouse Work to isolate parser and features

Comments

@KathleenDollard
Copy link
Contributor

KathleenDollard commented May 5, 2024 •
edited

RawInput was added to PipelineResult because it might make it easier to do errata. No longer sure it is useful, and it will not be available for args arrays.

Consider dropping
@KathleenDollard KathleenDollard changed the title Determine if we should track rawinput, Consider if/how we should track RawInput May 5, 2024
@KathleenDollard KathleenDollard added the Powderhouse Work to isolate parser and features label May 7, 2024
@KathleenDollard
Copy link
Contributor Author

Adding info:

The text entered for each value result is held in the Location. We need the info, but in theory we could rebuild from ValueResult

@mhutch mhutch added the Design label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Design Powderhouse Work to isolate parser and features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mhutch @KathleenDollard