-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Ability to configure re-frame-10x through project.clj #202
Comments
I've thought about this a little bit while developing 10x, and until recently I would have been 100% for this. Now with the new AOT cache, I think this approach is going to be unsafe? I would really like to be able to do this kind of feature, but am not sure how best to do it. Closure Defines could also work, but might be a little bit ugly. |
I see! In that article, it looks like I guess the config would look something like this in the defines case(?):
|
@Dexterminator were you able to get the |
@carylee that was just a proposal, it hasn't been implemented yet. In the meantime, you could do something in JavaScript which wrote to local storage the default values you'd like to have. I know it's not ideal, but could be a workaround for now. |
A quote from the linked article:
Seems like it's relevant if and only if someone decides to build a full JAR with re-frame-10x and then use re-frame-10x from that JAR. I'd think that such a scenario is so rare that anyone attempting it should simply be aware of the dragons ahead and not expect anything. |
We have a bunch of events (periodically polling ones) that we always want to ignore. Right now every developer has to manually enter these into the re-frame-10x settings panel. It would be very nice to be able to keep this config in version control, perhaps by allowing configuration in
project.clj
(that is then overridable in the re-frame-10x panel?).I think something similar to how cljs-devtools solves this would be nice: https://github.com/binaryage/cljs-devtools/blob/master/docs/configuration.md
Example config:
The text was updated successfully, but these errors were encountered: