mildlygeeky/craft_kint

Adds Kint, an in-app PHP debugger, to Craft CMS for use in Twig and PHP.

A Bit More Than Mildly Geeky

Hello! My name is Patrick Harrington and I run Mildly Geeky, a Boston-based web development firm.

We develop intuitive, accessible websites in Craft CMS, WordPress, and Laravel. We work with clients in and around Boston, as well as across the country.

craft_kint's Issues

Request: Can we get a Craft3 Beta version?

It would be nice to have craft_kint for the new Craft3 Beta. I've heavily relied on this lib in my Craft 2x projects. I feel somewhat lost without it in Craft3. This is a nice to have plugin.

Theme settings have additional space in UI

Not a big issue at all, but you can add first: true to the form macro on the Theme setting dropdown to make the field fit more nicely in the settings page UI.
https://github.com/mildlygeeky/craft_kint/blob/master/kint/templates/settings.html

Nice touch with the included themes. Aante Light is my favorite ;-)

Consider making variables into Twig functions

Currently, we can use the kint plugin on template variables like so:

{{ craft.kint.dd(entry) }}

It would be possible to shorten that a good bit by updating the variables to be Twig functions instead:

{{ dd(entry) }}

Doesn't seem to work in Craft 2.6

I saw the note the this plugin was aimed at Craft 2.4 / 2.5, and as I should have know might happen, when I installed it under Craft 2.6.2784, it didn't appear in the plugins panel, so I guess it's not compatible with Craft 2.6.

Would you consider upgrading this plugin such that it does work with Craft 2.6?

Code in output

Hi Patrick

as per slack, on my homepage if I

{% set test = 'blah' %}
   {{ craft.kint.d(test) }}

I am seeing some unparsed js:

"),b.document.close()},w=function(a,b){function c(a){var c=1===b?a.replace(/^#/,""):a;if(isNaN(c))return a.trim().toLocaleLowerCase();c=parseFloat(c);return isNaN(c)? a.trim():c}var d=a.tBodies[0];[].slice.call(a.tBodies[0].rows).sort(function(a,d){a=c(a.cells[b].textContent);d=c(d.cells[b].textContent);return ad?1:0}).forEach(function(a){d.appendChild(a)})},x=function(a){var b=document.querySelector(".kint-focused");b&&m(b,"kint-focused");if(-1!==a){b=e[a];l(b,"kint-focused");var c=function(a){return a.offsetTop+(a.offsetParent?c(a.offsetParent):0)};window.scrollTo(0,c(b)-window.innerHeight/2)}f=a},y=function(a,b){a?0>--b&&(b=e.length-1):++b>=e.length&& (b=0);x(b);return!1};window.addEventListener("click",function(a){var b=a.target,c=b.nodeName.toLowerCase();if(t(b)){if("dfn"===c)g(b),b=b.parentNode;else if("var"===c)b=b.parentNode,c=b.nodeName.toLowerCase();else if("th"===c)return a.ctrlKey||w(b.parentNode.parentNode.parentNode,b.cellIndex),!1;if("li"===c&&"kint-tabs"===b.parentNode.className)return"kint-active-tab"!==b.className&&(s(b),-1!==f&&u()),!1;if("nav"===c)return"footer"===b.parentNode.nodeName.toLowerCase()?(b=b.parentNode,k(b)?m(b):l(b)): setTimeout(function(){0a&&(d=a);p

→$debug Craft\Commerce_OrderModel(32)

Screenshot for proof ;) :

Consider updating default order of object tabs

When I use craft.kint.dd() in my template on an EntryModel, the order of the Kint tabs presented in the output are:

• Contents
• Available Methods
• Static Class Properties
• Iterator Contents

On first glance, with this scenario, my preferred order would be:

• Iterator Contents
• Available Methods
• Contents
• Static Class Properties

The Contents tab mostly has private and protected properties which I'm unable to interact with. So I immediately have to select another tab. The Static Class Properties tab also doesn't have anything I can interact with easily, so while I don't mind the info provided by these tabs, it seems the best place for them is farther down the list of tabs so I don't have to take an extra step each time.

The remaining two tabs are quite handy. Iterator Contents provides a list of things I can immediately interact with in the loop. (I wish the name was a bit more user friendly, but I feel that's true most of the time with everything). And Available Methods provides several public methods I could use or consider using.

Not sure if it is possible, or desirable for everyone, but my vote would be to prioritize the Iterator Contents and Available Methods tabs as I could see them coming in handy more often than the other tabs while debugging.