Skip to content

Commit cfbf2f2

Browse files
committed
Initial structure + tests
0 parents  commit cfbf2f2

File tree

109 files changed

+3611
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

109 files changed

+3611
-0
lines changed

.gitattributes

+39
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# This file is understood by git 1.7.2+.
2+
3+
# Windows specific files should always be crlf on checkout
4+
*.bat text eol=crlf
5+
*.cmd text eol=crlf
6+
*.ps1 text eol=crlf
7+
8+
# Check out the following as ln always for osx/linux/cygwin
9+
*.sh text eol=lf
10+
11+
# Opt in the following types to always normalize line endings
12+
# on checkin and always use native endings on checkout.
13+
*.config text
14+
*.cs text diff=csharp
15+
*.csproj text
16+
*.md text
17+
*.msbuild text
18+
*.nuspec text
19+
*.pp text
20+
*.ps1 text
21+
*.sln text
22+
*.tt text
23+
*.txt text
24+
*.xaml text
25+
*.xml text
26+
27+
# Binary files
28+
*.bmp binary
29+
*.jpeg binary
30+
*.jpg binary
31+
*.nupkg binary
32+
*.png binary
33+
*.sdf binary
34+
35+
*.java linguist-language=Dart
36+
*.kt linguist-language=Dart
37+
*.swift linguist-language=Dart
38+
*.m linguist-language=Dart
39+
*.h linguist-language=Dart

.github/FUNDING.yml

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
github: Baseflow
2+
custom: https://baseflow.com/contact
+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
3+
name: 🔙 Regression
4+
about: Report unexpected behavior that worked previously
5+
---
6+
7+
## 🔙 Regression
8+
9+
<!--- Summary description of the regression --->
10+
11+
### Old (and correct) behavior
12+
13+
### Current behavior
14+
15+
### Reproduction steps
16+
17+
### Configuration
18+
19+
**Version:** 1.x
20+
21+
**Platform:**
22+
- [ ] :iphone: iOS
23+
- [ ] :robot: Android
+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
3+
name: 🐛 Bug Report
4+
about: Create a report to help us fix bugs and make improvements
5+
---
6+
7+
## 🐛 Bug Report
8+
9+
<!--- Summary description of the bug --->
10+
11+
### Expected behavior
12+
13+
### Reproduction steps
14+
15+
### Configuration
16+
17+
**Version:** 1.x
18+
19+
**Platform:**
20+
- [ ] :iphone: iOS
21+
- [ ] :robot: Android
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
3+
name: 🚀 Feature Request
4+
about: Want to see something new included in the Framework? Submit it!
5+
---
6+
7+
## 🚀 Feature Requests
8+
9+
<!--- Summary description of the feature --->
10+
11+
### Contextualize the feature
12+
<!--- Where does it fit in the framework and why it's being included there. --->
13+
14+
### Describe the feature
15+
<!--- Use as much detail as possible here! --->
16+
17+
### Platforms affected (mark all that apply)
18+
- [ ] :iphone: iOS
19+
- [ ] :robot: Android
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
3+
name: 🏗 Enhancement Proposal
4+
about: Proposals for code cleanup, refactor and improvements in general
5+
---
6+
7+
## 🏗 Enhancement Proposal
8+
9+
<!--- A clear and concise description for your idea --->
10+
11+
### Pitch
12+
13+
<!--- How will this refactor improve contributors' lives? Input as many details as possible! --->
14+
15+
### Platforms affected (mark all that apply)
16+
- [ ] :iphone: iOS
17+
- [ ] :robot: Android

.github/ISSUE_TEMPLATE/e-question.md

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
3+
name: 💬 Questions and Help
4+
about: If you have questions, please use this for support
5+
---
6+
7+
## 💬 Questions and Help
8+
9+
For questions or help we recommend checking:
10+
11+
- The [Flutter tag in Stack Overflow](https://stackoverflow.com/questions/tagged/flutter)

.github/PULL_REQUEST_TEMPLATE.md

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
### :sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
2+
3+
4+
### :arrow_heading_down: What is the current behavior?
5+
6+
7+
### :new: What is the new behavior (if this is a feature change)?
8+
9+
10+
### :boom: Does this PR introduce a breaking change?
11+
12+
13+
### :bug: Recommendations for testing
14+
15+
16+
### :memo: Links to relevant issues/docs
17+
18+
19+
### :thinking: Checklist before submitting
20+
21+
- [ ] All projects build
22+
- [ ] Follows style guide lines ([code style guide](https://github.com/Baseflow/flutter-geocoder/blob/master/CONTRIBUTING.md))
23+
- [ ] Relevant documentation was updated
24+
- [ ] Rebased onto current develop

.gitignore

+98
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
# Miscellaneous
2+
*.class
3+
*.lock
4+
*.log
5+
*.pyc
6+
*.swp
7+
.DS_Store
8+
.atom/
9+
.buildlog/
10+
.history
11+
.project
12+
.svn/
13+
bin/
14+
coverage/
15+
16+
# IntelliJ related
17+
*.iml
18+
*.ipr
19+
*.iws
20+
.idea/
21+
22+
# Android Studio related
23+
android/.classpath
24+
android/.settings/
25+
example/android/.settings/
26+
27+
# Visual Studio Code related
28+
.vscode/
29+
30+
# Flutter repo-specific
31+
/bin/cache/
32+
/bin/mingit/
33+
/dev/benchmarks/mega_gallery/
34+
/dev/bots/.recipe_deps
35+
/dev/bots/android_tools/
36+
/dev/docs/doc/
37+
/dev/docs/lib/
38+
/dev/docs/pubspec.yaml
39+
/packages/flutter/coverage/
40+
version
41+
42+
# Flutter/Dart/Pub related
43+
**/doc/api/
44+
.dart_tool/
45+
.flutter-plugins
46+
.packages
47+
.pub-cache/
48+
.pub/
49+
build/
50+
flutter_*.png
51+
linked_*.ds
52+
unlinked.ds
53+
unlinked_spec.ds
54+
flutter_export_environment.sh
55+
**/.flutter-plugins-dependencies
56+
57+
# Android related
58+
**/android/**/gradle-wrapper.jar
59+
**/android/.gradle
60+
**/android/captures/
61+
**/android/gradlew
62+
**/android/gradlew.bat
63+
**/android/local.properties
64+
**/android/**/GeneratedPluginRegistrant.java
65+
66+
# iOS/XCode related
67+
**/ios/**/*.mode1v3
68+
**/ios/**/*.mode2v3
69+
**/ios/**/*.moved-aside
70+
**/ios/**/*.pbxuser
71+
**/ios/**/*.perspectivev3
72+
**/ios/**/*sync/
73+
**/ios/**/.sconsign.dblite
74+
**/ios/**/.tags*
75+
**/ios/**/.vagrant/
76+
**/ios/**/DerivedData/
77+
**/ios/**/Icon?
78+
**/ios/**/Pods/
79+
**/ios/**/.symlinks/
80+
**/ios/**/profile
81+
**/ios/**/xcuserdata
82+
**/ios/.generated/
83+
**/ios/Flutter/App.framework
84+
**/ios/Flutter/Flutter.framework
85+
**/ios/Flutter/Generated.xcconfig
86+
**/ios/Flutter/app.flx
87+
**/ios/Flutter/app.zip
88+
**/ios/Flutter/flutter_assets/
89+
**/ios/ServiceDefinitions.json
90+
**/ios/Runner/GeneratedPluginRegistrant.*
91+
**/ios/Flutter/Flutter.podspec
92+
93+
# Exceptions to above rules.
94+
!**/ios/**/default.mode1v3
95+
!**/ios/**/default.mode2v3
96+
!**/ios/**/default.pbxuser
97+
!**/ios/**/default.perspectivev3
98+
!/packages/flutter_tools/test/data/dart_dependencies_test/**/.packages

CODE_OF_CONDUCT.md

+74
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, gender identity and expression, level of experience,
9+
nationality, personal appearance, race, religion, or sexual identity and
10+
orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [[email protected]](mailto:[email protected]). All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at [http://contributor-covenant.org/version/1/4][version]
72+
73+
[homepage]: http://contributor-covenant.org
74+
[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
Contributing to the Flutter Geolocator plugin
2+
=============================================
3+
4+
What you will need
5+
------------------
6+
7+
* A Linux, Mac OS X, or Windows machine (note: to run and compile iOS specific parts you'll need access to a Mac OS X machine);
8+
* git (used for source version control, installation instruction can be found [here](https://git-scm.com/));
9+
* The Flutter SDK (installation instructions can be found [here](https://flutter.io/get-started/install/));
10+
* A personal GitHub account (if you don't have one, you can sign-up for free [here](https://github.com/))
11+
12+
Setting up your development environment
13+
---------------------------------------
14+
15+
* Fork `https://github.com/BaseflowIT/flutter-geolocator` into your own GitHub account. If you already have a fork and moving to a new computer, make sure you update you fork.
16+
* If you haven't configured your machine with an SSH key that's known to github, then
17+
follow [GitHub's directions](https://help.github.com/articles/generating-ssh-keys/)
18+
to generate an SSH key.
19+
* Clone your forked repo on your local development machine: `git clone [email protected]:<your_name_here>/flutter-geolocator.git`
20+
* Change into the `flutter-geolocator` directory: `cd flutter-geolocator`
21+
* Add an upstream to the original repo, so that fetch from the master repository and not your clone: `git remote add upstream [email protected]:BaseflowIT/flutter-geolocator.git`
22+
23+
Running the example project
24+
---------------------------
25+
26+
* Change into the example directory: `cd example`
27+
* Run the App: `flutter run`
28+
29+
Contribute
30+
----------
31+
32+
We really appreciate contributions via GitHub pull requests. To contribute take the following steps:
33+
34+
* Make sure you are up to date with the latest code on the master:
35+
* `git fetch upstream`
36+
* `git checkout upstream/develop -b <name_of_your_branch>`
37+
* Apply your changes
38+
* Verify your changes and fix potential warnings/ errors:
39+
* Check formatting: `flutter format .`
40+
* Run static analyses: `flutter analyze`
41+
* Run unit-tests: `flutter test`
42+
* Commit your changes: `git commit -am "<your informative commit message>"`
43+
* Push changes to your fork: `git push origin <name_of_your_branch>`
44+
45+
Send us your pull request:
46+
47+
* Go to `https://github.com/BaseflowIT/flutter-geolocator` and click the "Compare & pull request" button.
48+
49+
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)