-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add DataStores class to questionnaire store #1228
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Started looking though this but some changes look quite strange, like in placeholder_parser
was this done with a tool? I think it's had some unintended effects
a31f5c1
to
f6b1b51
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do a second pass but from a first look only found two small things 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finished going through now - just a few more small things
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great from what I can see & understand! Just had a couple of learning questions but no worries if there's not enough time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything resolved except one minor thing off a previous comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My comments all fixed 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not done an in-depth re-review, only a quick scan, mostly looks all okay. Noticed QS is inconsistent with attribute access, some private, some public, metadata has a setter, others doesn't, one to sort out in a future PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do have mixed feelings about this change but in general I think the change is for the better. I think we've accepted that we have sacrificed some readability for maintainability/extendibility.
LGTM 👍
What is the context of this PR?
This PR encapsulates all our questionnaire store's data stores into single
DataStores
class. I've added the optional methods to initialiseValueSourceResolver
,RuleEvaluator
,PlaceholderRenderer
to further reduce repetition. New class is kept in questionnaire store module for now, just to get it working in the first pass but happy to move it out.How to review
Running functional and unit tests plus some manual checks in live schemas and visual code checks should be sufficient.
Checklist