Conditiional Database project configuration switch #23
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 3 commits
January 17, 2024 12:39
A "Ticket" section was added to the pull request template. This change provides a space for developers to add the link that connects the pull request to its related issue. This will make tracking easier and increase the visibility of related work.
This commit involves the removal of the database-specific solutions, i.e., MSSQL and Postgre, from the project. It includes the deletion of configuration files, project references, test setup files, and exception handling components pertaining to these solutions. With these deleted, the project setup is streamlined, and only the main solution remains.
The API solution template documentation has been updated to include an optional switch for the creation of a PostgreSQL database configuration. Additional command explanation and file structure changes have been outlined for further clarity. The necessary modifications for running Docker-compose in your project have also been specified.
added 3 commits
January 17, 2024 19:59
Added boolean configuration parameters to enable choice between MSSQL and Postgre in the database and model configuration templates. Also, updated relevant .cs files to conditionally use configurations based on these parameters. Modified the pull request template to have a correct ticket link syntax.
The model configuration documentation has been updated to include more detailed instructions for generating a new Model Configuration class for PostgreSQL databases. An additional optional parameter `--usePOSTGRE` has been introduced. This option, along with the existing parameters, has been listed out for better visibility. A typo in the code example has also been fixed.
This update changes the 'Database project template' page in the documentation. It introduces how to generate a PostgreSQL project using the `--usePOSTGRE` switch. Furthermore, it explains several additional switches that users can utilize when creating their database project.
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.
Ticket
22
What type of PR is this? (check all applicable)
Rationale
Currently the ability exists to create database projects for either MSSQL or PostgreSQL, so we wanted to make it easier to generate new solutions and define the target Database engine.
Implementation
Implemented additional switches command on the project generation making use of the Conditional processing and comment syntax , to enable the addition of conditional, or dynamic, content you can add Template Engine expressions in your source files. The conditional expression let you to include or exclude part of the file according to a specified condition, and to do this you can use the familiar conditional expressions like
#if, #else, #elseif, #endif.Refactored the project templates to make use this functionality