-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: HCL Support #6
Comments
You know, I started thinking about this just 2 days ago :) There are two key points here:
|
Note that implementing the HCL support may get a bit tricky, as HCL seems to be ambiguous and that needs to be sorted out in the first place [1]. The pyhcl implementation of dumping pretty much depends on that, so I'll wait until [1] is resolved and then go on with implementing this. (I sorted out the second point by creating https://github.com/bkabrda/anymarkup-core and making anymarkup be pretty much only "meta-package" to install all the dependencies + anymarkup-core itself. I released that work in 0.5.0 and would welcome testing/comments.) [1] hashicorp/hcl#24 |
Probably need a new issue for this, but TBH, I think you should include all the markups by default to make for a better first time user experience. I can't imagine it is all that much disk or time to install them all. However, once someone wants to move to production (or whatever) or becomes a "power user" the ability to remove markups they don't use would be nice. However, as I re-read your remark, maybe that is what you said? :) |
So here's what I did:
Effectively, there is no visible change for people who just install "anymarkup" - and that is still the preferred way. The only change is that you can choose to install anymarkup-core with only a limited set of parsers, if you really need to do that for a reason. |
Github needs a "like" button. +1 |
You can always tweet about how awesome I am (and I have twitter account now - https://twitter.com/slavek_k - , so that makes as cool as anyone else!) |
I may have to wait for the HCL support ;) |
Hashicorp developed HCL as an alternative to JSON and YAML and allows its use with some of their tools. As some of our tools use anymarkup and interact with some Hashicorp tools, I would like anymarkup to support HCL.
The text was updated successfully, but these errors were encountered: