plainoldrecipe
validate-configs-action
| plainoldrecipe | validate-configs-action | |
|---|---|---|
| 2 | 3 | |
| 303 | 14 | |
| - | - | |
| 6.4 | 6.3 | |
| 20 days ago | 6 months ago | |
| Python | Dockerfile | |
| GNU Affero General Public License v3.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
plainoldrecipe
-
Ask HN: What was an interesting project you started and finished over a weekend?
I built a website that takes online recipe pages and just returns the main recipe in plain text. https://www.plainoldrecipe.com
-
Wait, What's a Bookmarklet?
Bookmarklets are great in mobile browsers. This is handy if you want to avoid writing an extension for a simple script.
I use a bookmarklet I wrote all the time to remove the extra content from online recipes: https://github.com/kevlened/foodmarklet
It’s based on https://github.com/poundifdef/plainoldrecipe, but it works entirely in the client.
validate-configs-action
-
Ask HN: What was an interesting project you started and finished over a weekend?
Took me bout 2 days for the initial release of the config-file-validator. I had been thinking about it for a while and was able just to knock it pretty quickly
https://github.com/Boeing/config-file-validator
-
Have multiple config file types in a project? Here’s a single tool to validate them all!
Project Link: https://github.com/Boeing/config-file-validator
-
GitHub Action to scan for config files in your repo and validate the syntax
Github Action to use the config-file-validator (https://github.com/Boeing/config-file-validator) to recursively scan the directory structure of a repo for config files and validate their syntax as part of a CI/CD pipeline.
This is useful as a quick quality gate in your CI pipeline to validate that a syntax error was not introduced in the latest commit. Currently XML, JSON, YAML, INI, and TOML are supported with CSV, HCL, and Plist coming in the next release.
Here's how to add it to your existing workflow: https://github.com/kehoecj/validate-configs-action/tree/main...
What are some alternatives?
Force-Paste - Paste text even when not allowed (password dialogs etc) in macOS
config-file-validator - Cross Platform tool to validate configuration files
awesome-bookmarklets - 🔖 Awesome collection of helpful bookmarklets
figcone - Read JSON, YAML, TOML, XML or INI configuration by declaring a struct
foodmarklet - Bookmarklet version of plainoldrecipe
structured-text-tools - A list of command-line tools for manipulating structured text data
bookmarklet-platform - A platform for distributing JS bookmarklets created from GitHub gists
parse_it - A python library for parsing multiple types of config files, envvars & command line arguments that takes the headache out of setting app configurations.
web-automation
gookit/config - 📝 Go configuration manage(load,get,set,export). support JSON, YAML, TOML, Properties, INI, HCL, ENV and Flags. Multi file load, data override merge, parse ENV var. Go应用配置加载管理，支持多种格式，多文件加载，远程文件加载，支持数据合并，解析环境变量名
payday
uxf - Uniform eXchange Format (uxf) is a plain text human readable optionally typed storage format that supports custom types. It may serve as a convenient alternative to csv, ini, json, sqlite, toml, xml, or yaml.