Commit d4e187cf authored by Brian Egan's avatar Brian Egan

Getting some of the basics in place

parent ac41a093
# Contributing
Contributions are very welcome in many forms :)
## Issues
If you find a problem with any of the examples, please [file an issue on Gitlab](
## Merge Requests
If you would like to fix a bug or make an improvement, please [file a merge request]( explaining your changes!
For larger changes, such as a including a new app, please submit an Issue before you
begin or submit a "Work In Progress" Merge request that gives an overview of the changes you'd
like to make and the reasoning behind it!
### Code Hygiene
* Ensure your updates follow the app spec
* Ensure your code is properly formatted with `dartfmt`
* Please ensure tests are up to date
* Verify `dartanalyzer` isn't throwing any warning or errors/
# Contributor 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
## Our Standards
Examples of behavior that contributes to creating a positive environment
* 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
* 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. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and 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 [][version]
\ No newline at end of file
...@@ -175,4 +175,11 @@ To make this concrete, Let's see how our callbacks flow in the this app. ...@@ -175,4 +175,11 @@ To make this concrete, Let's see how our callbacks flow in the this app.
| Screen | | Screen |
| | | |
+----------------+ +----------------+
``` ```
\ No newline at end of file
## Addendum
Since Flutter is quite similar to React with regards to State management, many of the resources on the React site are pertinent when thinking about State in flutter. In fact, the ideas in this example were lifted directly from the React site:
* [Lifting State Up in React](
* [Thinking in React](
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment