-
Notifications
You must be signed in to change notification settings - Fork 84
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
feat: Add campaign module and banners #3240
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Pull Request Test Coverage Report for Build 12886743242Details
💛 - Coveralls |
…e memory footprint
@@ -62,7 +62,7 @@ export default defineConfig(({ mode }) => { | |||
commonjsOptions: { | |||
transformMixedEsModules: true | |||
}, | |||
sourcemap: true | |||
sourcemap: false |
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.
Removing the sourcemaps is a tradeoff that we need to take at this moment, as building the distributable in vercel is quite impossible.
@@ -38,6 +38,7 @@ import CollectionRow from './CollectionRow' | |||
import { Props, TABS } from './CollectionsPage.types' | |||
import './CollectionsPage.css' | |||
|
|||
const BUILDER_BANNER_ID = 'builderCampaignBanner' |
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.
should we move this const to modules/common/types
?
This PR adds the new campaign module and the code to display the banners and use the campaign data from the module.
It also removes all of the old code that was used to display the banners.
The configurations are only set on dev, as the final entities and keys are to be set before the release.