-
Notifications
You must be signed in to change notification settings - Fork 4
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
Deploy contribution tool across different hosts #172
Conversation
d93ce1c
to
6114dd7
Compare
src/pages/service.tsx
Outdated
return JSON.parse( | ||
JSON.stringify({ | ||
props: { | ||
...props, | ||
documentTypes: await getDocumentTypes(), | ||
documentTypes: TERMS_TYPES.default || TERMS_TYPES, |
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.
Why can't we know exactly how to load the data?
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.
We know, it was just to make it resilient for futur updates if we change how it is exported as we do not want to maintain this code, but I can simplify it if you prefer?
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.
Since we have now locked dependencies versions, such a change would need a voluntary update in the codebase so I don't see much point in future-proofing at this stage. Up to you 🙂
Also update engine and load terms-types as a dependency