Skip to content

Commit cb0f2e8

Browse files
sergejcodessergejcodes
authored
v2.3.0
2 parents cdd0ba9 + 505585c commit cb0f2e8

File tree

14 files changed

+5614
-1038
lines changed

14 files changed

+5614
-1038
lines changed

‎.config/.stylelintrc.js

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
module.exports = {
2+
extends: 'stylelint-config-recommended',
3+
plugins: [
4+
/**
5+
* docs: https://stylelint.io/user-guide/configure#plugins
6+
*/
7+
// 'stylelint-scss' // not included by default, add with a package manager
8+
],
9+
ignoreFiles: [
10+
/**
11+
* docs: https://stylelint.io/user-guide/configure#ignorefiles
12+
*/
13+
// 'my-file.css',
14+
// '**/my-directory/*.css'
15+
],
16+
rules: {
17+
/**
18+
* docs: https://stylelint.io/user-guide/rules/list
19+
*/
20+
'at-rule-no-unknown': [
21+
true,
22+
{
23+
ignoreAtRules: [
24+
'tailwind',
25+
'apply',
26+
'variants',
27+
'responsive',
28+
'screen'
29+
]
30+
}
31+
],
32+
'no-descending-specificity': null
33+
}
34+
}

‎.config/plugins/shopify/theme.init.js

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,12 @@ const options = commandLineArgs(optionDefinitions)
2424
// check the provided options
2525
if (Object.keys(options).length < 4) {
2626
console.error(chalk.red('not enough arguments provided for initialization'))
27-
process.exit(1)
27+
process.exit()
2828
}
2929

30-
if (!options.env.match(/^dev$|^live$|^staging$/)) {
31-
console.error(chalk.red('env should be \'dev\', \'live\' or \'staging\''))
32-
process.exit(1)
30+
if (!options.env.match(/^(dev|live)$/)) {
31+
console.error(chalk.red(`env should be ${chalk.inverse('dev')} or ${chalk.inverse('live')}`))
32+
process.exit()
3333
}
3434

3535
/**
@@ -54,7 +54,7 @@ const initTheme = async () => {
5454
themeId = response.data.theme.id.toString()
5555
} catch (e) {
5656
console.error(chalk.red(e))
57-
process.exit(1)
57+
process.exit()
5858
}
5959

6060
// create yaml config
@@ -75,7 +75,7 @@ const initTheme = async () => {
7575
await fs.outputFile(configPath, yamlConfig)
7676
} catch (e) {
7777
console.error(chalk.red(e))
78-
process.exit(1)
78+
process.exit()
7979
}
8080

8181
// write settings_data.json to shopify/config
@@ -105,7 +105,7 @@ const initTheme = async () => {
105105
}
106106
} catch (e) {
107107
console.error(chalk.red(e))
108-
process.exit(1)
108+
process.exit()
109109
}
110110

111111
// upload Shopify theme to remote
@@ -116,10 +116,10 @@ const initTheme = async () => {
116116
})
117117
} catch (e) {
118118
console.error(chalk.red(e))
119-
process.exit(1)
119+
process.exit()
120120
}
121121

122-
console.log(chalk.green('initialized remote theme'))
122+
console.log(chalk.green('✓ theme successfully initialized'))
123123
}
124124

125125
/**

‎.config/shopify/shopify.sample.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
11
# this is a sample file for illustration purposes and can be safely deleted
22
# run shopify:init to initialize a new Shopify config
3+
#
4+
# if you are manually initializing the local config:
5+
# don't forget to set the correct environment on the next line, either 'dev:' or 'live:'
36
dev:
47
password: [your-api-password]
58
theme_id: "[your-theme-id]"

‎.config/webpack/webpack.dev.js

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
const path = require('path')
22
const { merge } = require('webpack-merge')
33
const ESLintPlugin = require('eslint-webpack-plugin')
4+
const StylelintPlugin = require('stylelint-webpack-plugin')
45
const common = require('./webpack.common.js')
56
const log = require('../plugins/log')
67

@@ -57,6 +58,13 @@ module.exports = merge(common, {
5758
new ESLintPlugin({
5859
files: 'src/**/*.{js,vue}',
5960
overrideConfigFile: path.resolve(__dirname, '../.eslintrc.js')
61+
}),
62+
/**
63+
* docs: https://www.npmjs.com/package/stylelint-webpack-plugin
64+
*/
65+
new StylelintPlugin({
66+
files: 'src/**/*.{vue,css,sass,scss}',
67+
configFile: path.resolve(__dirname, '../.stylelintrc.js')
6068
})
6169
]
6270
})

‎.github/CODE_OF_CONDUCT.md

Lines changed: 132 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,132 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
contact@sergej.codes.
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
120+
121+
Community Impact Guidelines were inspired by
122+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+
124+
For answers to common questions about this code of conduct, see the FAQ at
125+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
126+
at [https://www.contributor-covenant.org/translations][translations].
127+
128+
[homepage]: https://www.contributor-covenant.org
129+
[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
130+
[Mozilla CoC]: https://github.com/mozilla/diversity
131+
[FAQ]: https://www.contributor-covenant.org/faq
132+
[translations]: https://www.contributor-covenant.org/translations

‎.github/CONTRIBUTING.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
## Contributing guide
2+
Please take a moment to read this document in order to make the contribution process easy and effective for everyone.
3+
4+
### Project goals
5+
> **Shopify Theme Lab** was built to provide a great developer experience while crafting Shopify themes.
6+
7+
#### This project aims to be:
8+
- **Modular** - It should be effortless to alter, add, remove or swap any component.
9+
- **Fast** - Automating tedious processes as much as possible.
10+
- **Intuitive** - This project as a whole, file contents and directory structure should be quick to grasp and easy to work with.
11+
- **Self-sufficient** - There should be no need to install external tools or applications outside of the project to make it work.
12+
- **Modern** - Gone are the days of jQuery.
13+
14+
Please keep the above points in mind when submitting issues or adding new features.
15+
16+
### Bug reports
17+
A good bug report should be easy to understand and as detailed as possible. Explanations on how to reproduce the problem and/or screenshots are a great help.
18+
19+
### Feature requests
20+
Before submitting a feature request try to find out whether your idea fits with the scope and aims of the project. Provide as much detail and context as possible.
21+
22+
### Pull requests
23+
Good pull requests - patches, improvements, new features - are a great help. They should remain focused in scope and avoid containing unrelated commits.
24+
25+
**Please ask first** before starting any significant pull request (e.g. implementing new features, refactoring code), otherwise you risk spending a lot of time working on something that might not be merged into the project.
26+
27+
Also follow to the coding conventions used throughout the project (indentation, comments, etc.).
28+
29+
> All pull requests should be submitted to the `dev` branch, **not** the `master` branch.

‎.github/ISSUE_TEMPLATE/bug-report.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
name: Bug report
3+
about: Report a bug report.
4+
title: ''
5+
labels: 'bug-report'
6+
assignees: ''
7+
---
8+
9+
<!-- 👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible. -->
10+
11+
### Version and operating system
12+
13+
<!-- Example: v2.0.0 on Windows 10 -->
14+
15+
### Description
16+
17+
<!-- Text -->
18+
19+
<details open>
20+
<summary>Additional Details</summary>
21+
<br>
22+
<!-- Attachments -->
23+
</details>
24+
25+
### Steps to reproduce
26+
27+
<!-- Text -->
28+
29+
### What is Expected?
30+
31+
<!-- Text -->
32+
33+
### What is actually happening?
34+
35+
<!-- Text -->

‎.github/ISSUE_TEMPLATE/config.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: false

‎.github/ISSUE_TEMPLATE/feature-request.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea or enhancement.
4+
title: ''
5+
labels: 'feature-request'
6+
assignees: ''
7+
---
8+
9+
### Is your feature request related to a problem? Please describe.
10+
11+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
12+
13+
### Describe the solution you'd like
14+
15+
<!-- A clear and concise description of what you want to happen. Adding some code examples would be neat! -->
16+
17+
### Describe alternatives you've considered
18+
19+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
20+
21+
### Additional context
22+
23+
<!-- Add any other context or screenshots about the feature request here. -->

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
<!-- PULL REQUEST TEMPLATE -->
2+
<!-- (Update "[ ]" to "[x]" to check a box) -->
3+
4+
**What kind of change does this PR introduce?** (check at least one)
5+
- [ ] Bugfix
6+
- [ ] Feature
7+
- [ ] Code style update
8+
- [ ] Refactor
9+
- [ ] Other, please describe:
10+
11+
**Does this PR introduce a breaking change?** (check one)
12+
- [ ] Yes
13+
- [ ] No
14+
15+
If yes, please describe the impact and migration path for existing applications:
16+
17+
**The PR fulfills these requirements:**
18+
- [ ] It's submitted to the `dev` branch, _not_ the `master` branch
19+
20+
If adding a **new feature**, the PR's description includes:
21+
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)
22+
23+
**Other information:**

0 commit comments

Comments
 (0)