(Documentation) secondary package structure
See original GitHub issueType of Issue
[ X] Bug Report
[ ] Feature Request
Description
please describe the error that you encountered The documentation for secondary package shows the sub package (testing) under source, while it seems that it actually needs to be directly under the package. This is how the angular modules are built.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Package Structure - GitLab Docs
Debian packages. Debian contains a higher number of dedicated tables, so it is displayed here separately: projects namespaces packages_packages ...
Read more >Package Structure - an overview | ScienceDirect Topics
Organizing requirements into packages corresponding to various specifications provides familiarity and consistency with document-based approaches and ...
Read more >4 Package structure and state
1). Files that drive package development, checking, and documentation, outside of CRAN's purview. Examples: Files relating to the RStudio IDE.
Read more >4. Package structure and distribution
However, Python also supports a second type of package known as a “namespace package”. Namespace packages are a way of splitting a single...
Read more >Project documentation and structure — ORIE 6125
Project structure ¶ · doc , referring to the documentation of the code in the repository. There are two subdirectories here: one that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have read it again and again, and I am not sure what are the correct wording to describe this. I am not yet familiar with sub packages. The one missing clarification is probably explaining that the module Id is the “main” entry in package.json. Closing for now.
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
This action has been performed automatically by a bot.