This PR moves all types except code tables directly under the crate root, without type name changes.
This makes incompatible changes to the API.
Due to my own unfamiliarity in the early stages of development, the library crate exposed the internal module hierarchy to the outside world as is.
However, this makes it difficult to refactor with internal hierarchical structure changes.
From the user's point of view, it is also difficult to grasp the full picture of what types exist in the API documentation.
This change solves these problems and will help future refactoring.
As for the code tables, I continue to keep the modules separate, as I plan to add various types (which should be machine-generated in the future), and putting them in the same level as the other types for data processing will bury the other types.
This PR moves all types except code tables directly under the crate root, without type name changes. This makes incompatible changes to the API.
Due to my own unfamiliarity in the early stages of development, the library crate exposed the internal module hierarchy to the outside world as is. However, this makes it difficult to refactor with internal hierarchical structure changes. From the user's point of view, it is also difficult to grasp the full picture of what types exist in the API documentation. This change solves these problems and will help future refactoring.
As for the code tables, I continue to keep the modules separate, as I plan to add various types (which should be machine-generated in the future), and putting them in the same level as the other types for data processing will bury the other types.