Merge branch 'develop'

Author: ololx

.gitignore

@@ -1,18 +1,15 @@
-# Xcode
-#
-# gitignore contributors: remember to update Global/Xcode.gitignore, Objective-C.gitignore & Swift.gitignore
+########### Xcode ###########
+# Xcode temporary files that should never be committed
 
-## User settings
-xcuserdata/
+## Build generated
+build/
+DerivedData
 
-## compatibility with Xcode 8 and earlier (ignoring not required starting Xcode 9)
-*.xcscmblueprint
-*.xccheckout
+# NB: NIB/XIB files still exist even on Storyboard projects, so we want this
+*~.nib
+*.swp
 
-## compatibility with Xcode 3 and earlier (ignoring not required starting Xcode 4)
-build/
-DerivedData/
-*.moved-aside
+## Various settings
 *.pbxuser
 !default.pbxuser
 *.mode1v3
@@ -21,32 +18,47 @@ DerivedData/
 !default.mode2v3
 *.perspectivev3
 !default.perspectivev3
+xcuserdata
 
-## Obj-C/Swift specific
-*.hmap
+## Other
+*.xccheckout
+*.moved-aside
+*.xcuserstate
+*.xcscmblueprint
+*.xcscheme
 
-## App packaging
-*.ipa
-*.dSYM.zip
-*.dSYM
+########### Mac OS X ###########
+# Mac OS X temporary files that should never be committed
 
-## Playgrounds
-timeline.xctimeline
-playground.xcworkspace
+.DS_Store
+.AppleDouble
+.LSOverride
 
-# Swift Package Manager
-#
-# Add this line if you want to avoid checking in source code from Swift Package Manager dependencies.
-# Packages/
-# Package.pins
-# Package.resolved
-# *.xcodeproj
-#
-# Xcode automatically generates this directory with a .xcworkspacedata file and xcuserdata
-# hence it is not needed unless you have added a package configuration file to your project
-# .swiftpm
+# Icon must end with two \r
+Icon
+
+
+# Thumbnails
+._*
 
-.build/
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+########## Objective-C/Swift specific ##########
+*.hmap
+*.ipa
 
 # CocoaPods
 #
@@ -55,36 +67,17 @@ playground.xcworkspace
 # https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
 #
 # Pods/
-#
-# Add this line if you want to avoid checking in source code from the Xcode workspace
-# *.xcworkspace
 
 # Carthage
 #
 # Add this line if you want to avoid checking in source code from Carthage dependencies.
 # Carthage/Checkouts
 
-Carthage/Build/
-
-# Accio dependency management
-Dependencies/
-.accio/
+Carthage/Build
 
 # fastlane
 #
-# It is recommended to not store the screenshots in the git repo.
-# Instead, use fastlane to re-generate the screenshots whenever they are needed.
-# For more information about the recommended setup visit:
-# https://docs.fastlane.tools/best-practices/source-control/#source-control
+# It is recommended to not store the screenshots in the Git repository. Instead, use fastlane to re-generate the
 
 fastlane/report.xml
-fastlane/Preview.html
-fastlane/screenshots/**/*.png
-fastlane/test_output
-
-# Code Injection
-#
-# After new code Injection tools there's a generated folder /iOSInjectionProject
-# https://github.com/johnno1962/injectionforxcode
-
-iOSInjectionProject/
+fastlane/screenshots

BADGES_GUIDE.md

@@ -0,0 +1,47 @@
+# Badges Guide
+
+This section presents a some badges reference guide from the [readme](README.md) file, which are project activity info and are not widely distributed or are attached special for this project.
+
+## Status
+
+Status is an informational badge which shows the project development activity. This information can be represented by the following statuses:
+
+- `active` - this means that the project is under active development.
+- `frozen` - this means that the project is still under development, but all work on it was temporarily suspended to clarify and formalize new ideas.
+- `completed` - this means that the project implements the intended functionality and the development is completed. Development can be resumed if new ideas for an improvements or features appear.
+
+If you want to help in development, you have any feature suggestions for the project or if you faced a problem or bug, please visit the [contributing](CONTRIBUTING.md) section.
+
+## Version
+
+This information represents the actual version of the project. For the versioning is used [SemVer](http://semver.org/).
+
+## Stable
+
+Stable is an informational badge which shows the api interface stability. This information can be represented by the following:
+
+- `yes` - this means that the project in a stable state.
+- `no` - this means that the project is not in a stable state and some interfaces could be changed.
+
+## OSS Lifecycle
+
+OSS Lifecycle is an initiative started by Netflix to classify open-source projects into lifecycles  and clearly identify which projects are active and which ones are retired. To enable this badge,  simply create an `OSSMETADATA` tagging file at the root of your GitHub repository containing a  single line similar to the following: `osslifecycle=active`. Other suggested values are  `osslifecycle=maintenance` and `osslifecycle=archived`. A working example  can be viewed on the [OSS Tracker repository](https://github.com/Netflix/osstracker).
+
+## Maintenance
+
+This is an informational badge which shows the maintenance process state of the project. The following statuses are applied:
+
+- `yes` - this means that the project is under maintenance.
+- `no (of {expiration date})` - this means that the project is no longer maintained.
+
+In both cases, the project can still be used.
+
+Please visit the [contributing](CONTRIBUTING.md) page if you faced with some issues with the project.
+
+## Release Date
+
+This is an information about the project release date which would be stable and could be used. In this case, it is possible to indicate the date of the first release, last release, release of a specific version.
+
+## Commit Date
+
+This is an information about the project commit date, which would show the last commit date in the project repository.

CHANGELOG.md

@@ -0,0 +1,18 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to [Semantic Versioning](http://semver.org/).
+
+## [Unreleased] - yyyy-mm-dd
+
+### Changed
+
+- Refactor application.
+
+## [0.0.1-alpha] - 2021-11-03
+
+### Added
+
+- The `Finder extension`  which allows to:
+  - create new empty file.

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations