Skip to content

Possible Refactor For Parser Error Messages - #165

Draft
ianjosephwilson wants to merge 4 commits into
t-strings:mainfrom
ianjosephwilson:ian/prep_for_custom_errors_part6_remix
Draft

Possible Refactor For Parser Error Messages#165
ianjosephwilson wants to merge 4 commits into
t-strings:mainfrom
ianjosephwilson:ian/prep_for_custom_errors_part6_remix

Conversation

@ianjosephwilson

Copy link
Copy Markdown
Contributor

@davepeck This is a possible refactor of the other branch ( #164 ) where we pull out all the non-essential error handling into a helper class. Sorry I had sent the other PR yesterday from what I've been rebasing/rehashing but I got restless and started fiddling with it again.

The TemplateParser still decides which exceptions to raise but the ParsingErrorHelper does all the noisy (awful, tedious, etc.) stuff. I'm not committed to this separation but the parser is drowning in methods already.

A good sign I think is that the actual source extraction and that "weird" value check both only are triggered from the helper class.

@davepeck

Copy link
Copy Markdown
Contributor

Thanks @ianjosephwilson -- plan to look at this soon! Will consider #164 vs #165 along the way.

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.

2 participants