cuelm VS pls

We've started working on a tool to use CUE to create a single config space across TF, Helm, and other tools in the devops space.

https://github.com/hofstadter-io/cuelm

Our hypothesis is that a unified config space across our industry will bring many benefits.

Our open questions are largely around whether we

(1) replace / alternative

(2) just a skin, still same reconciliation loop from the tools

(3) replace, but support existing modules & charts

Thanks for the share! Very timely

We are in the process of introspecting TF to produce CUE schemas. Maybe this can help us cuetify user TF as well

if you are curious: https://github.com/hofstadter-io/cuelm (it has expanded in scope since inception to include the likes of TF and other areas of e2e CI)

Many PR about typos fixing or installing GitHub actions to validate spellchecking on various repositories fix typos #4 ccoVeille posted on Apr 15, 2024 Fix typos and style Format README.md file View on GitHub Add Typos GitHub Action #37 ccoVeille posted on Apr 19, 2024 https://github.com/marketplace/actions/typos-action Fixes #28 View on GitHub fix typos #113 ccoVeille posted on Apr 13, 2024 Fix typos in code and tests Fix acronyms and brand names View on GitHub fix typos, brands and acronyms #21 ccoVeille posted on Apr 01, 2024 fix typos in code, test and documentation Fix registered trademark and other acronyms View on GitHub Fix typos in the documentation and code comments #99 ccoVeille posted on Apr 21, 2024 View on GitHub typos suggestion #390 ccoVeille posted on Apr 22, 2024 Check list [X] I have performed a self-review of my code [ ] I have commented my code in hard-to-understand areas [X] I have made corresponding changes to the documentation Description Fix some typos and wordings in README.md Fix headers style Fix exemplī grātiā usage (Latin) Type of change [ ] Bug fix [ ] New feature [ ] Refactor [ ] Breaking change [X] Documentation change Test environment Shell [ ] bash [ ] zsh [ ] fish OS [ ] Linux [ ] Mac OS X [ ] Windows [ ] Others: View on GitHub Fix typo and style #3 ccoVeille posted on Apr 25, 2024 View on GitHub

I'm working on pls (https://github.com/dhruvkb/pls/), a prettier and more powerful alternative to ls(1) that adds a lot of customisation and provides a very fluent command-line interface. It aims to be a superset of exa in terms of the features, while being more actively maintained and targeting a smaller subset of pro-users.

It works quite well and is very usable as a daily driver. I'm adding more features to it and making it available to install it via platform-native package managers.

I made a small CLI tool called pls (repo). It's a FOSS app for listing the contents of your directory (similar to ls) but it has lots of nifty features geared towards professionals/programmers (hence the 'p' in the name) that make the output prettier and easier to visually parse.