-
Tiny differences in HTML, or behaviour that isn't quite the same.
The templates are being manually converted, and there are differences between Python and Go templating that emerge in subtle ways.
For example, python might have a 'not' function that evals some kind of false value. Whereas in Go it's really just doing a nil check. So the template may look right, but will actually behave differently.
Additionally I'm subtly changing the underlying models. In Django the field names and visibility suited the front-end, but in this I'm making the models be precisely the same as the ones inside the API to allow those to be shared in future. But it means that the models are just slightly different.
Another subtle thing is the length of truncation on text has come out different. The same values are in the old and new system, and you'd only notice with the old and new side by side... But I notice.
The HTML should be the same of course, but I started this 6 years ago and tweaked the Django one since, so they diverged and all needing checking.
Velocio-
So cruft is a kind of reference to ‘craft’ (what was intended to happen) but where the programmatic (instruction?) intention varies due to the instruction specified is subtlety different between the languages?
Apologies, didn’t mean to derail the thread but am fascinated by the termYou can probably guess in a fraction of a moment I have absolutely no grasp of all this stuff
crossedthread
Can I ask what ‘cruft’ is?
Nothing else on this thread makes any sense to me at all but I do like the sound of that word