Comments (3)
Hmmm - it's not supposed to be. It's a base class for NTP_conf and ChronyConf, so they both work the same way. It doesn't have a parser decorator for that reason. I certainly agree that both NTP_conf and ChronyConf need better documentation if they're going to refer to a class that doesn't exist, but I'd rather not mention the base class so as to prevent rule writers thinking they need to use that class.
How about I update the NTP_conf and ChronyConf documentation with a copy of the documentation in NTPConfParser? What's the best way of getting good documentation into the parsers that we want people to use?
from insights-core.
@PaulWay I think that until we have a new proposal on the table for how to best present the parsers in the documentation that we have to continue to include all code as we have in the past. If you want to create a branch and propose a new way to generate the docs then I think that would be the best way to effect change.
from insights-core.
OK.
from insights-core.
Related Issues (20)
- VDOStatus - excessive ParseException be raised against it HOT 1
- Spec modinfo_filtered_modules will raise CalledProcessError when the target module is not found HOT 1
- "get_filters" applies the filter to non-filterable dependency specs incorrectly
- ParseExceptions are not recorded in Broker HOT 1
- Memory leak in archive downloading
- Unhandled Exception in 'gluster_peer_status' parser HOT 1
- Collect AWS public IP and Hostname HOT 1
- Output of datasource `rpm_pkgs` cannot be handled correctly
- `meta_data` JSON file generated incorrect for some built-in file
- A bug in parser "FSTab"
- Enhance Parser GrubbyDefaultKernel for some unexpected command output
- `InstalledRpms` parser is unable to parse the file `rpm-qa` when it contains a warning HOT 1
- Too many IndexError in PartedL HOT 1
- Custom built/third party RPMs may not be parsed correctly
- The mdstat parser doesn't parse the device up indication correctly HOT 1
- Uname padding release section of version seems backwards when missing "el" portion
- Doc rst file for parsers/sys_block.py is missing
- Datasource leapp_report was skipped due to no 'remediations' in 'detail' HOT 2
- Exception: TypeError: '<' not supported between instances of 'str' and 'int' HOT 1
- ConfigCombiner cannot handle 'include' path not include /* HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from insights-core.