The improvements are complete and seem to be working on the unit tests.
This branch contains a series of hacks and changes which culminate in several large changes. The overall time-line is:
Much work and hacking including an intermediate site API and other attempts.
Remove code which has not been used or updated in a while: 07fedc910462987366f96a3a82d6edf8047b6988, c27c722dc562404620149f995943707fb2691fec, 8fb387176592bbd2a5f4ab71f23ea6d63f3c2ca9.
Replace site API: 5914169dd40174c0c37d6feffa052b06596a3b0e.
Update code to use new site API or compatibility layer: e05e17a55f7ec115469b5f2ac3d68d07426c3532, 9544c12265fea38bae14900fec8aece1778c61d4.
Clean up and fixes to get the new API fully working.
The diff is very large and reviewing the original commits is not going to be effective. The best approach is to check the diff from master: git diff -D -w master materializable-contexts. Or just let me explain it to you and we can discuss it.
Since github doesn't seem to show it, here is the diffstat:
John, as we discussed I don't think a normal review will be effective. Let's plan to go through it together. I do want your input and thoughts to make sure I haven't done anything super dumb.
The improvements are complete and seem to be working on the unit tests.
This branch contains a series of hacks and changes which culminate in several large changes. The overall time-line is:
The diff is very large and reviewing the original commits is not going to be effective. The best approach is to check the diff from master:
git diff -D -w master materializable-contexts
. Or just let me explain it to you and we can discuss it.Since github doesn't seem to show it, here is the diffstat: