We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Assuming
import ( parser "github.com/haproxytech/config-parser/v5" ) ... p := parser.New(content, options)
Currently it's possible to obtain the parsed models for all supported attributes like
log, err := p.Get(parser.Global, parser.GlobalSectionName, "log") // ([]types.Log, error) ...
It's also possible to update the data associated with the same attribute
err := p.Set(parser.Global, parser.GlobalSectionName, "log", log)
One can also render the full config using
p.String()
Proposal In one of our use cases, we would like to obtain the resulting lines from such updates for a given attribute path. So e.g.
lines, err := p.Render(parser.Global, parser.GlobalSectionName, "log")
Currently the lack of such granular access prevents us from effectively using the Config Parser code for our use case.
(Happily) wiling to contribute code if this feature makes sense.
The text was updated successfully, but these errors were encountered:
this is what Result function is doing in parsers right?, its just that is not exposed or available
if you are willing to contribute, we can discuss that (on objections on feature as long as it does not bring large complexity)
Sorry, something went wrong.
No branches or pull requests
Assuming
Currently it's possible to obtain the parsed models for all supported attributes like
It's also possible to update the data associated with the same attribute
One can also render the full config using
Proposal
In one of our use cases, we would like to obtain the resulting lines from such updates for a given attribute path.
So e.g.
Currently the lack of such granular access prevents us from effectively using the Config Parser code for our use case.
(Happily) wiling to contribute code if this feature makes sense.
The text was updated successfully, but these errors were encountered: