Thirdly, adding a new icon requires a bunch of boilerplate. Also, there’s already a lack of consistency between the naming conventions (Logo vs Icon anyone?). Only half a dozen icons and this approach is already becoming unwieldy. Here’s the folder structure after adding the first handful of SVG icons to A2k: This equates to two files and a lot of shared code per icon. I would also need to create another file to register the component. I recognized one such undesirable pattern for how A2k handled icons.įor each icon added, I would create a file with the web component boilerplate + the contents of the SVG. As an organic project grows larger, some unwanted patterns start to emerge. Many small projects, like A2k, grow organically. For other projects, it’s important to consider how the project’s architecture may positively or negatively impact the project over time. ![]() I’ve been gradually making changes when I get some time, but haven’t given much consideration to certain aspects of the library’s architecture.įor something small and scrappy, like a prototype or a proof-of-concept, testing an idea quickly is better than coding it perfectly. Name Andrico Karoulla the past few months, I’ve been working on a small UI library called A2k.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |