use flask way to manage config#2693
Open
anshulagrawal2902 wants to merge 1 commit intoOpen-MSS:developfrom
Open
use flask way to manage config#2693anshulagrawal2902 wants to merge 1 commit intoOpen-MSS:developfrom
anshulagrawal2902 wants to merge 1 commit intoOpen-MSS:developfrom
Conversation
ReimarBauer
reviewed
Mar 15, 2025
|
|
||
| def create_app(name="", imprint=None, gdpr=None): | ||
| imprint_file = imprint | ||
| gdpr_file = gdpr |
Member
|
Welcome @anshulagrawal2902 Thx for working on this. Have a look on the failing tests. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose of PR?:
Fixes #2506
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Does this PR results in some Documentation changes?
If yes, include the list of Documentation changes
Checklist:
<type>: <subject>