Nette 2.3 introduced LinkGenerator, enabling link generation outside of presenters. Here's a step-by-step guide to wiring it up with Latte templates and factories to produce emails with fully working {link} and n:href macros, including a CLI tip for absolute URLs.
The January meetup in Prague featured workshops for all skill levels and attracted over 120 attendees. The highlight of the evening was David Grudl presenting the hot-off-the-press Nette 2.3 beta release.
This patch release fixes several notable bugs: FileMock now numbers files sequentially to prevent collisions, Environment::lock() properly supports multiple locks, and –stop-on-fail works during the initial phase. The –info output has also been streamlined.
FileMock improvements, a new `-o` command-line option for flexible output formatting (console, TAP, or none), and the biggest addition — full HHVM support starting from version 3.3.0.
Version 2.2.3 brings calling Latte filters outside of templates, full error logging in Tracy, a safer debug mode with a cookie safeguard, excluding classes from autowiring, and suppression of output buffer warnings. Five new features worth paying attention to.
The original repository has been split into 19 standalone components with their own repositories and versioning. For users, almost nothing changes – but now Latte, Tracy, the database, and anything else can be used completely independently. In addition, this version brings a number of new features in forms, database, and templates.
Code coverage HTML reports, 33 parallel threads by default, a new FileMock class for emulating files in memory, recursive structure comparison, and the ability to combine @dataProvider with @testCase and @multiple — here's a overview of what's new.
A recap of two spring 2014 working meetups covering VPS preparation, Addons Portal fixes, the new default directory structure RFC, plans for standalone project websites, and the IProvider modular concept for extending extensions.
The redesigned portal now supports Packagist packages, loads dependencies from composer.json, and accepts both Texy! and Markdown descriptions. Most existing addons have been migrated, and the entire portal is released as an open-source Nette application.
Key topics included the upcoming Addons portal deployment, the long-awaited splitting of Nette Framework into smaller repositories, and cherry-picking commits for the Nette Framework 2.1.2 release. Martin Major takes over as Nette Boss for the next month.
A recap of the second Nette Foundation meetup from February 2014: what we accomplished since January — the official blog, Tester 1.0 release, Latte/Tracy/Database separation — and what's next, including the new Addons Portal and documentation updates.
You already write tests every day — every time you var_dump a result to check if it's correct. Instead of deleting that code, let it work for you. Nette Tester turns this habit into real automated testing.
After four years of development, Nette Tester has grown into a stable testing tool featuring parallel execution, code coverage analysis, integrated NetBeans 8.0 support, and a clean, easy-to-use API.
New low-level API for working with data, CheckboxList element, rendering via n:name attributes, partial rendering, smarter validators with dynamic references to other elements, and simplified creation of custom elements. An overview of all the important changes.
A simple OOP wrapper for JSON sounds easy, but PHP's json_* functions are riddled with bugs and quirks. Here's a robust implementation that works around unreliable error reporting, UTF-8 detection issues, and other surprising pitfalls.
Property injection is tempting for its brevity – it eliminates boilerplate constructor code. However, it has serious drawbacks: public properties don't ensure type checking or immutability. We would need read-only public properties with type checking, which PHP 8.1 ultimately delivered.
Constructor, methods, or public variables? Every way of passing dependencies has its pitfalls – immutability, inheritance, boilerplate code. I break down why even constructor injection isn't without problems and what could help.
Service locator looks like a handy way of passing dependencies, but in reality it's an antipattern. I explain why it violates the principle of explicit dependencies, and show how to distinguish legitimate constructs from a real service locator.
When do DI and lazy loading come into conflict, and why is the factory-based solution actually flawed? The right approach is an accessor that returns the dependency without presuming how it was created.
Hidden dependencies make code unpredictable and confusing. Yet DI is a surprisingly simple technique – just stop hiding dependencies and start passing them explicitly. Through practical examples, I show why it's worth it and how to do it.
Generating HTML tags “on the fly” leads to messy and error-prone code. Nette\Utils\Html solves this with an intuitive object-oriented interface featuring a fluent API for working with elements, attributes, and their children.
You've reached the end.
