Skip to content

Commit fe94363

Browse files
ahmednfwelaahmednfwela
authored
Merge branch 'main' into main
2 parents b531c86 + b0f8d3c commit fe94363

18 files changed

+409
-103
lines changed

‎.github/ISSUE_TEMPLATE/---bug.md

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
name: "\U0001F41B Bug"
3+
about: Something is crashing or not working as intended
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
## Environment
11+
12+
**Package version:**
13+
14+
<details>
15+
<summary>Flutter doctor</summary>
16+
17+
<!-- Paste the output of running `flutter doctor -v` below inside ``` and ``` -->
18+
```
19+
```
20+
21+
</details>
22+
23+
<details>
24+
<summary>Code sample</summary>
25+
26+
<!--
27+
Please create a minimal reproducible sample that shows the problem
28+
and attach it below between the lines with the backticks.
29+
30+
You can use a example code or Flutter sample app
31+
32+
Without this we will unlikely be able to progress on the issue, and because of that
33+
we regretfully will have to close it.
34+
-->
35+
36+
```dart
37+
```
38+
39+
</details>
40+
41+
## Description
42+
43+
**Expected behavior:**
44+
45+
**Current behavior:**
46+
47+
## Steps to reproduce
48+
49+
1. This
50+
2. Than that
51+
3. Then
52+
53+
## Images <!-- if available, else delete -->
54+
55+
## Stacktrace/Logcat <!-- if available, else delete -->

‎.github/ISSUE_TEMPLATE/---documentation.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: "\U0001F4C3 Documentation"
3+
about: You want to report something that is wrong or missing from the documentation
4+
title: ''
5+
labels: documentation
6+
assignees: ''
7+
8+
---
9+
10+
### Describe the change you would like to see
11+
<!-- A clear and concise description of the bug or documentation you feel is missing.
12+
For example: The Technical Reference does not include information about the FormBuilderFilterChip widget. -->
13+
14+
### How would the suggested change make the documentation more useful?
15+
<!-- Provide context for how the requested change would make the docs easier to use and improve your ability to develop successful applications with this packages.
16+
For example: It's hard to know a method exists or understand its use when you have to search through the code base to learn about it. Properly documenting it in the Technical Reference makes it easier for me to know what the flutter_fom_builder is (and is not capable of). -->
17+
18+
### Additional context
19+
<!-- Add any other context about your feedback here.
20+
For example: I am reading the docs directly from GitHub, so it's harder for me to find information on a particular method if it's not included in the documentation. -->

‎.github/ISSUE_TEMPLATE/---feature-request.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: "\U0001F680 Feature request"
3+
about: Suggest new feature or request for this project
4+
title: ''
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
## Environment
11+
12+
**Package version:**
13+
14+
## Description
15+
16+
**What you'd like to happen:**
17+
18+
**Alternatives you've considered:** <!-- if available, else delete -->
19+
20+
**Images:** <!-- if available, else delete -->

‎.github/ISSUE_TEMPLATE/---questions-and-help.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
name: "\U0001F914 Questions and help"
3+
about: You have a question or need help using this package
4+
title: ''
5+
labels: question
6+
assignees: ''
7+
8+
---
9+
10+
## Describe your question
11+
<!-- A clear and concise description of your question or help wanted.
12+
For example: How can I add a datetime field? -->

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
## Connection with issue(s)
2+
3+
<!-- If this pull request close some issue, use this reference to close it automatically -->
4+
Close #???
5+
6+
<!-- Optional: other issues or pull requests related to this, but merging should not close it -->
7+
Connected to #???
8+
9+
## Solution description
10+
11+
## Screenshots or Videos
12+
13+
<!-- Optional: to clearly demonstrate the feature or fix to help with testing and reviews -->
14+
15+
## To Do
16+
17+
- [ ] Read [contributing guide](https://github.com/flutter-form-builder-ecosystem/form_builder_image_picker/blob/main/CONTRIBUTING.md)
18+
- [ ] Check the original issue to confirm it is fully satisfied
19+
- [ ] Add solution description to help guide reviewers
20+
- [ ] Add unit test to verify new or fixed behaviour
21+
- [ ] If apply, add documentation to code properties and package readme

‎.github/workflows/base.yaml

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
name: Base
2+
3+
on:
4+
push:
5+
branches: [main]
6+
7+
pull_request:
8+
branches: [main]
9+
10+
workflow_dispatch:
11+
12+
jobs:
13+
build:
14+
runs-on: macos-latest
15+
16+
steps:
17+
- uses: actions/checkout@v3
18+
19+
- name: Check broken links
20+
uses: JustinBeckwith/linkinator-action@v1
21+
with:
22+
paths: "**/*.md"
23+
24+
- name: Flutter action
25+
uses: subosito/flutter-action@v2
26+
with:
27+
channel: 'stable'
28+
flutter-version: '2.10.5'
29+
30+
- name: Install dependencies
31+
run: flutter pub get
32+
- name: Format code
33+
run: flutter format --dry-run --set-exit-if-changed .
34+
- name: Analyze static code
35+
run: flutter analyze
36+
# - name: Run tests
37+
# run: flutter test
38+
- name: Build example
39+
run: |
40+
cd example
41+
flutter build appbundle --debug
42+
flutter build ios --debug --no-codesign
43+
flutter build web

‎.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@
88
.buildlog/
99
.history
1010
.svn/
11+
/.fvm
1112

1213
# IntelliJ related
1314
*.iml

‎CODE_OF_CONDUCT.md

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

‎CONTRIBUTING.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
# Contributing
2+
3+
Thank you for considering and taking the time to contribute to this project!
4+
5+
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with collaborators of this repository before making a change.
6+
7+
Please note we have a [code of conduct](https://github.com/flutter-form-builder-ecosystem/form_builder_image_picker/blob/main/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
8+
9+
## How to Contribute
10+
11+
First setup repository to contribute
12+
13+
If you already setup repository, take a look at the issues and take a stab at them. We'll try to make the issue as verbose as possible, so it is easy for you to help. When you're done, create a [Pull Request](https://github.com/flutter-form-builder-ecosystem/form_builder_image_picker/compare).
14+
15+
You don't need to code to help us. If you have a suggestion of a feature, see a bug or a thing that should be improved, [open an issue](https://github.com/flutter-form-builder-ecosystem/form_builder_image_picker/issues/new/choose) on Github.
16+
17+
18+
## Setup development environment
19+
20+
### Copy repository
21+
22+
* Fork `https://github.com/flutter-form-builder-ecosystem/form_builder_image_picker/` into your own GitHub account. If you already have a fork and moving to a new computer, make sure you update you fork.
23+
* If you haven't configured your machine with an SSH key that's known to github, then
24+
follow [GitHub's directions](https://help.github.com/articles/generating-ssh-keys/)
25+
to generate an SSH key.
26+
* Clone your forked repo on your local development machine: `git clone [email protected]:<your_name_here>/form_builder_image_picker.git`
27+
* Add an upstream to the original repo, so that fetch from the master repository and not your clone: `git remote add upstream [email protected]:flutter-form-builder-ecosystem/form_builder_image_picker.git`
28+
29+
### Running the example project
30+
31+
* Change into the example directory: `cd example`
32+
* Run the App: `flutter run`
33+
34+
## Implement code
35+
36+
### Enhancement (new feature or request)
37+
38+
- Implement code
39+
- Implement unit tests
40+
- Add example
41+
- Test example in all package compatible platforms
42+
- Are a new behaviour; add to readme package
43+
44+
### Bug
45+
46+
- Fix bug
47+
- Update and/or add unit tests to verify fixed behaviour
48+
- Verify if bug is fixed all package compatible platforms
49+
50+
## Make a pull request
51+
52+
We really appreciate contributions via GitHub pull requests. To contribute take the following steps:
53+
54+
* Make sure you are up to date with the latest code on the main:
55+
* `git fetch upstream`
56+
* `git checkout upstream/main -b <name_of_your_branch>`
57+
* Apply your changes
58+
* Verify your local changes and fix potential warnings/errors:
59+
* Check formatting: `flutter format .`
60+
* Run static analyses: `flutter analyze`
61+
* Run tests: `flutter test`
62+
* Commit your changes: `git commit -am "<your informative commit message>"`
63+
* Push changes to your fork: `git push origin <name_of_your_branch>`
64+
* Open a pull request and fill template
65+
66+
Please make sure you solved all warnings and errors reported by the static code analyses and that you fill in the full pull request template. Failing to do so will result in us asking you to fix it.

0 commit comments

Comments
 (0)