- Drupal 8 Module Development
- Daniel Sipos
- 263字
- 2021-07-02 12:22:41
Which way to link?
As we saw, we have a number of ways to create links and URL representations, but when it comes to creating a link, which method should we use? There are advantages and disadvantages to each one.
When it comes to URL, as mentioned, it's a good idea to stick to hardcoding routes rather than URIs. However, if you are working with dynamic data, such as user input or stored strings, the other methods are perfectly valid. I recommend that you look at the Url class in detail because you will be using it quite a bit as you develop Drupal 8 modules.
Regarding the actual links, using the service to generate a link means that you are creating a string at that point in the code. This means that it cannot be altered later in the process. However, using the Link class falls nicely in line with the entire render array rationale of delaying the actual generation to the last possible moment. We will talk more about render arrays later on. So, the choice you make depends on the link you need to generate and your answer to the following question: is the link something that might have to be alterable by other modules/themes? If so, proceed with the render array. Otherwise, you might consider generating if you can inject the service properly.
When it comes to entities, it's always better to use the helper methods on the base entity classes to generate links and URLs to these entities. We will talk more about entities later in this book.
- Mastering Entity Framework Core 2.0
- HTML5移動Web開發技術
- Java EE 6 企業級應用開發教程
- 軟件界面交互設計基礎
- Boost C++ Application Development Cookbook(Second Edition)
- C語言程序設計基礎與實驗指導
- Hands-On Data Structures and Algorithms with JavaScript
- Python金融數據分析
- 名師講壇:Java微服務架構實戰(SpringBoot+SpringCloud+Docker+RabbitMQ)
- Haskell Data Analysis Cookbook
- 青少年信息學競賽
- Mastering C++ Multithreading
- Node.js開發指南
- Vue.js光速入門及企業項目開發實戰
- Application Development with Swift