feat(dashboard): select tracker variants #117
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR 4/? for #9.
This adds a new settings page for managing the tracker and also having a convenient spot within the application to copy and paste the tracker code.
Rather than going for the approach of other solutions where the user updates the script name to something like
script.feature-1.feature2.feature-3.js, we've opted for a cleaner interface with justscript.jswhere the user selects the features from the dashboard.The trade-off is that it will take up to 6 hours for caches to be revalidated on returning visitors to have the new script, but it allows for much much more flexibility and ease of use for the end user to change and update features at will. It also makes it much much easier for us to add new features that are more granular and optimal for the user.
This PR also continues the work of migrating many components off Mantine UI to unstyled native or Radix components for a faster, cleaner, and smaller implementation. It's better to make these big changes now so we have a solid foundation to build off in the future. This one focuses on replacing inputs (
TextInputandPasswordInput) to a native alternative instead.