commit 201f96a0afdfd9cce13fd10b3a51ecf8235579f8 Author: Flatlogic Bot Date: Thu Mar 12 16:06:58 2026 +0400 Initial import diff --git a/light-blue-vue-master/.gitignore b/light-blue-vue-master/.gitignore new file mode 100644 index 0000000..366086a --- /dev/null +++ b/light-blue-vue-master/.gitignore @@ -0,0 +1,21 @@ +.DS_Store +node_modules +dist + +# local env files +.env.local +.env.*.local + +# Log files +npm-debug.log* +yarn-debug.log* +yarn-error.log* + +# Editor directories and files +.idea +.vscode +*.suo +*.ntvs* +*.njsproj +*.sln +*.sw* \ No newline at end of file diff --git a/light-blue-vue-master/CODE_OF_CONDUCT.md b/light-blue-vue-master/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..dc1d288 --- /dev/null +++ b/light-blue-vue-master/CODE_OF_CONDUCT.md @@ -0,0 +1,46 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. + +Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@flatlogic.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] + +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/ diff --git a/light-blue-vue-master/CONTRIBUTING.md b/light-blue-vue-master/CONTRIBUTING.md new file mode 100644 index 0000000..3af80e2 --- /dev/null +++ b/light-blue-vue-master/CONTRIBUTING.md @@ -0,0 +1,120 @@ +# Contributing to Light Blue + +Your contributions are welcome and are greatly appreciated! Every little bit helps, and credit +will always be given. + +Please take a moment to review this document in order to make the contribution process easy and +effective for everyone involved. + +## Conduct + +Please, follow the [golden rule](https://en.wikipedia.org/wiki/Golden_Rule). Be respectful, even to +those that are disrespectful. + +## Feedback + +Feedback is the breakfast for champions! We'd love to hear your opinions, discuss potential +improvements, architecture, theory, internal implementation, etc. Please, join or start a new +conversation in our [issue tracker](https://github.com/flatlogic/light-blue-vue-admin/issues). + +## Documentation + +We need your help with improving documentation to the project. This might be the easiest way for +you to contribute, because you don't even need to clone the repo but can edit or create new `.md` +files right from GitHub website as described [here](https://help.github.com/articles/editing-files-in-your-repository/). + +## Bugs & Feature Requests + +Before opening an issue, please: + +* Check [Documentation](https://demo.flatlogic.com/light-blue-vue-admin/documentation). +* Search the [issue tracker](https://github.com/flatlogic/light-blue-vue-admin/issues) to make sure + your issue hasn’t already been reported. +* If your issue sounds more like a question, please post it on StackOverflow.com instead with the + tag [sing-app](http://stackoverflow.com/questions/tagged/light-blue-vue-admin). + +## Pull Requests + +Before you submit a [pull request](https://help.github.com/articles/using-pull-requests/) from your +forked repo, check that it meets these guidelines: + +* If the pull request adds functionality, the docs should be updated as part of the same PR. +* Create a separate PR for each small feature or bug fix. +* [Squash](http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git) + your commits into one for each PR. +* When contributing to an opt-in feature, apply the `[feature/...]` tag as a prefix to your PR title + +## Style Guide + +We follow [Airbnb's Style Guide](https://github.com/airbnb/javascript) for best practices writing javascript code. + +## Commit Message Guidelines + +We have very precise rules over how our git commit messages can be formatted. This leads to **more +readable messages** that are easy to follow when looking through the **project history**. But also, +we use the git commit messages to **generate the ngx-admin change log**. + +### Commit Message Format +Each commit message consists of a **header**, a **body** and a **footer**. The header has a special +format that includes a **type**, a **scope** and a **subject**: + +``` +(): + + + +