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
Meta data from .pod file #14
Comments
It would seem reasonable to prefer .pod over .pm, if you wouldn't want to use that it wouldn't be there. |
This is actually more tricky than expected, because some metadata ( |
Yes, I ran into that while testing possible proposals for code changes. While I've come up with a working scheme for "falling back" on the pm file In my situation, I'm working on generating POD from special comments - So, I've been working to enhance my POD generator to extract information That does lead to another to another idea I might propose. Still working on On Fri, Mar 25, 2016 at 3:04 PM, Leon Timmermans notifications@github.com
|
I don't understand what information you would want to extract from a .pod file if the .pm is present. Could you give an example? Also since the addition of the metamerge file it can be much easier to tweak up the discovered data with your own data. |
On Sat, Mar 26, 2016 at 3:18 PM, Joel Berger notifications@github.com
For various reasons, some projects put the documentation in a separate pod Thinking more, it occurs to me that, in the general case, supporting a For my situation, I could generate a metamerge.json file along side |
They don't. |
This has been fixed in 0.034 |
Please support reading the meta data from the .pod file, not just the .pm file. Maybe have a --pod option to request this.
The text was updated successfully, but these errors were encountered: