Has anyone developed a LookML code smells document? I know we have a couple of style guides and linters from @fabio and @Ryan_Tuck that sets out some guides and coding standards but I’m thinking about general coding best practices such as keeping code DRY and making use of inheritance, project structure, one view per file etc
If nothing else, I would welcome suggestions to be added to my style guide (and then PR’s to the linter )
Hey @Carl_Anderson! I haven’t necessarily seen anything like that outside of a handful of style guides I’ve seen. It seems like a linter could detect repetition, multiple views in one file, etc. Would also welcome any feature requests / PRs on our end via github issues on lookmlint.