Ab#6711 upgrade cloudykit/jet to 6.1.0 #118
Draft
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.
This is more of a proof of concept than anything else but given jet 2.1.1 is coming up 5 years old and there are some features we might like to take advantage of in later versions (some improvements to trim whitespace for example) I thought I'd see what would be involved in a/ making the tests run and b/ getting templates (specifically Curzon) to render.
a/ is definitely easier than b/ - the main difficulty is that templates are slurped in using NewSet() which can't be altered afterwards to insert strings masquerading as templates for testing, so the strings which were used as templates previously have been exported as files and are read in as part of this process.
Getting the templates to play ball is a harder proposition. It tends to be very unforgiving. You can see the changes required to get it working here https://github.com/indiereign/shift72-curzon/compare/master..e6ef680b2af7362bc7c2a87d810fca57c66c21d3. The main gotchas are
range item := itemswill be an array of indices without any items:=otherwise that's a paddlin'I know these are probably best practice anyway but it's quite confronting to see a wall of red error text on render.
I don't know whether the fact that all sites use the latest builder version by design or accident but if there was a reason to ensure sites are build with specific versions rather than whatever the latest one is, updating jet to this version might be it.
Jibin is looking into whether we can benchmark Kibble performance as a whole rather than individual packages and I wonder if we'll see many improvements with an update to jet.