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

How to handle survey-specific code? #441

Open
SachaG opened this issue Oct 25, 2024 · 0 comments
Open

How to handle survey-specific code? #441

SachaG opened this issue Oct 25, 2024 · 0 comments

Comments

@SachaG
Copy link
Member

SachaG commented Oct 25, 2024

Currently, results uses a lot of survey-specific code (components, configs, etc.) which is all imported using webpack alias. But that means it has to live in monorepo instead of surveys.

Config such as colors, etc. could potentially be made available through the API (even though this is not always ideal since it's more work compared to just importing; and also it's harder to ensure proper types), but that doesn't work for components such as a survey's animated logo.

Is there a way to import from the survey repo based on the currently active editionId in results's .env file?

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

No branches or pull requests

1 participant