refactor: split database module to submodules #152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 9 commits
January 3, 2023 18:43
|
|
arucil
approved these changes
Jan 6, 2023
Itou-Ng
approved these changes
Jan 6, 2023
arucil
pushed a commit
that referenced
this pull request
Feb 3, 2023
Submit a pull request for this project. <!-- If you have an Issue that related to this Pull Request, you can copy this Issue's description --> # Why? <!-- > Related to which issue? > Why we need this pull request? > What is the user story for this pull request? --> use multiple feature modules instead of database module https://github.com/vikadata/vikadata/issues/2659 # What? <!-- > Can you describe this feature in detail? > Who can benefit from it? --> split Database module into multiple submodules. ```mermaid graph TD; Database-->Application; Actuator-->Application; Automation-->Application; Fusion-->Application; Grpc-->Application; User-->Application;; Unit-->Application;; Developer-->Application;; Shared-->Database; Shared-->Actuator; Shared-->Automation; Shared-->Fusion; Shared-->Grpc; Shared-->User; Shared-->Unit; Shared-->Developer; Attachment-->Database; Dashboard-->Database; Datasheet-->Database; Form-->Database; Mirror-->Database; Resource-->Database; Shared-->Attachment; Shared-->Dashboard; Shared-->Datasheet; Shared-->Form; Shared-->Mirror; Shared-->Resource; ``` # How? <!-- > Do you have a simple description of how this pull request is implemented? --> - [x] split Database module into multiple submodules, such as attachment module, dashboard module, datasheet module, etc.
wumanho
pushed a commit
to wumanho/apitable
that referenced
this pull request
Feb 6, 2023
Submit a pull request for this project. <!-- If you have an Issue that related to this Pull Request, you can copy this Issue's description --> # Why? <!-- > Related to which issue? > Why we need this pull request? > What is the user story for this pull request? --> use multiple feature modules instead of database module https://github.com/vikadata/vikadata/issues/2659 # What? <!-- > Can you describe this feature in detail? > Who can benefit from it? --> split Database module into multiple submodules. ```mermaid graph TD; Database-->Application; Actuator-->Application; Automation-->Application; Fusion-->Application; Grpc-->Application; User-->Application;; Unit-->Application;; Developer-->Application;; Shared-->Database; Shared-->Actuator; Shared-->Automation; Shared-->Fusion; Shared-->Grpc; Shared-->User; Shared-->Unit; Shared-->Developer; Attachment-->Database; Dashboard-->Database; Datasheet-->Database; Form-->Database; Mirror-->Database; Resource-->Database; Shared-->Attachment; Shared-->Dashboard; Shared-->Datasheet; Shared-->Form; Shared-->Mirror; Shared-->Resource; ``` # How? <!-- > Do you have a simple description of how this pull request is implemented? --> - [x] split Database module into multiple submodules, such as attachment module, dashboard module, datasheet module, etc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Submit a pull request for this project.
Why?
use multiple feature modules instead of database module
https://github.com/vikadata/vikadata/issues/2659
What?
split Database module into multiple submodules.
graph TD; Database-->Application; Actuator-->Application; Automation-->Application; Fusion-->Application; Grpc-->Application; User-->Application;; Unit-->Application;; Developer-->Application;; Shared-->Database; Shared-->Actuator; Shared-->Automation; Shared-->Fusion; Shared-->Grpc; Shared-->User; Shared-->Unit; Shared-->Developer; Attachment-->Database; Dashboard-->Database; Datasheet-->Database; Form-->Database; Mirror-->Database; Resource-->Database; Shared-->Attachment; Shared-->Dashboard; Shared-->Datasheet; Shared-->Form; Shared-->Mirror; Shared-->Resource;How?