Jacek Tomaszewski

Agreed. To maintain current behaviour, the 'replace' strategy should be a default one, and 'merging' should be triggered by a metadata keyword, something like `^:join` or `^:merge` (it'd be the...

@kennyjwilli So I will provide a counter-example for your conclusion, based on my current need. It is something like you've described in discussion, but connected to `:closure-defines`. I have one...

Merging maps shouldn't be tricky: I think it's just a matter of replacing `merge` by `merge-with` https://github.com/adzerk-oss/boot-cljs/blob/master/src/adzerk/boot_cljs/middleware.clj#L43 Thank you for the `update-file` code; I'll give it a try, but for...

@kennyjwilli It seems to be working, however I needed to add `make-parents` call (proper comment in the gist).

Typical django admin log does only contain information about what changed, but no old/new values are logged. Will something like this suits you? "At changed "

I'd suggest to store the PK of the selected object (as a string) and have a custom logic that retrieves this dbsetting and fetches the actual entity. Would that work...

Sites framework will stay optional. Your error is strange since the migration lists its dependency on `sites`. Or have you added `sites` later, after you had performed initial migration for...

Thanks for the idea. I wonder why didn't you make a Pull Request. ;)

Thanks for the info and a bug-report link. Indeed some action need to be taken. Let me think a while.

@vahidm No update so far, but this message (warning) is only annoying, not harmful.