Chrome extension (Dev tools)

[kettanaito]

What

Need to develop a Google Chrome extension as a RAF DevTools.

Why

1. To allow logging form/field events outside of the console.
2. To get rid of numerous console.log statements.
3. For easier debugging and time-based form/field changes.
4. For potential time-travelling (applying the state of the form at the certain period of time).

How

1. Read how to develop a Chrome extension.
2. Well, develop it.

[kettanaito]

I gave it a try, and creating Chrome extension is easier than it seems. At least, at the first glance.

During the brainstorming I realized that the logged events must be grouped logically, which would make them easier to read and navigate. My initial thought is to have a "major" events (i.e. "change", "blur", "submit"), which are logged at the root level, and then "minor" events which may follow the major ones (i.e. "update", "validate").

Update: A spec should be written for this dev tool.

[kettanaito]

#354 will assist tremendously for such dev tool, since now each state update contains only the relevant patch of the next field(s). That patch is what needs to be displayed in the dev tool, to objectively see what field properties have changed.