Pull Request: Refactor and Rename Document Conversion to Document Generation #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This pull request encompasses several critical changes aimed at transitioning from the "Document Conversion" concept to "Document Generation." This includes renaming directory paths, updating workflow actions, and modifying documentation and library usage instructions to reflect the new terminology and directory structures. Additionally, new functionalities for presentation generation have been introduced to the existing document library.
Changes
Renaming Directories and Updating Workflow Paths:
/officegen-api
to/privateomega-lib
to align with new structural guidelines.Dependabot Configuration:
dependabot.yml
configuration to reflect the new directory structure. This ensures our dependencies are kept up-to-date automatically.GitHub Workflows:
publish-conversion.yml
for the Document Conversion NPM Package.publish-gen.yml
for the Document Gen NPM Package.Documentation Updates:
officegen-api
directory.Library Enhancements:
documentLibrary.js
, expanding the utility of the library beyond document generation.Test Adjustments:
Implications
This PR is a foundational step towards enhancing the flexibility and functionality of our NPM packages, ensuring they remain robust and scalable as we continue to expand our offerings.