Open
Conversation
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
1 participant
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.
Description:
To apply the Python formatter to the project, it will be done progressively. The goal is to split the project and create a branch to apply the formatter to each part. In this case, the formatter was applied to the ./video folder. This branch will be merged into the 'add-linter' branch. Once all parts have been fixed, the 'add-linter' branch will be merged into 'develop'.
Steps to test change/Steps to reproduce bug:
The changes that were made should be analyzed and it should be verified that only the format was changed. The project should be launched and its functionality tested superficially. Exhaustive testing will be done when the 'add-linter' branch is ready.