Skip to content
This repository has been archived by the owner on May 23, 2023. It is now read-only.

Commit

Permalink
Merge pull request #20 from madeiramadeirabr/feat/arquivos_git
Browse files Browse the repository at this point in the history
Atualização de arquivos voltados para a comunidade e gestão do projeto.
andersoncontreira authored Apr 2, 2022
2 parents c9eb58f + cc289b9 commit 11a05f0
Showing 63 changed files with 2,024 additions and 430 deletions.
60 changes: 41 additions & 19 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,45 +1,67 @@
---
name: Bug reports
about: Bug reports
title: bug - [component/module] - bug title
labels: ''
assignees: ''
name: Bug Report
about: File a bug report
title: "bug - [component/module] - bug title"
labels: "bug report"
assignees: ""
---

<!-- ## We appreciate you creating a new issue 😄!
## Thanks for creating an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
Please search open/closed issues before submitting. Someone might have asked the same thing before.
To help us, please take the time to accurately fill out this template. ❤️

-->
#### 1. Describe the bug:

#### 1. Bug description:
> A brief description of the issue.
> Ex: When I \_**\_, I expected \_\_** to happen but \_\_\_\_ happened instead.
> Enter a simple description about the bug
> Example: When I \_**\_, I expected the behavior \_\_** but the behavior \_\_\_\_ occurred
---

#### 2. Version:

> The version of this library that are using.
---

#### 3. Link to bug example:
#### 3. Link to Reproduction:

> Link to CodeSandbox or any sandbox service that shows the error happening (see https://github.com/accezar/multi-package-start#codesandbox-templates for examples)
> A link to a CodeSandbox or any other sandbox service which demonstrates the bug (see https://github.com/accezar/multi-package-start#codesandbox-templates for templates)
---

#### 4. Step-by-step to reproduces the error behavior:
#### 4. Steps to reproduce

> 1. Go to '...'
> 2. Click on '....'
> 3. Get the error
> 3. Scroll down to '....'
> 4. See error
---

#### 5. Screenshots

> Se possível, adicione screenshots para ajudar a explicar o erro
> If applicable, add screenshots to help explain your problem.
---

#### 6. Desktop (please complete the following information):

- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

---

#### 7. Smartphone (please complete the following information):

- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

---

#### 6. Extra info
#### 8. Additional context

> Add any additional information here that you think is relevant to understanding the issue
> Add any other context about the problem here.
75 changes: 75 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
name: "Bug Report"
description: "File a bug report"
labels: ["bug report"]
body:
- type: "markdown"
attributes:
value: |
Thanks for creating an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
We're all volunteers here, so help us help you by taking the time to
accurately fill out this template. ❤️
- type: "input"
id: "description"
attributes:
label: "Description"
description: "A brief description of the issue."
placeholder: |
When I ____, I expected ____ to happen but ____ happened instead.
validations:
required: true
- type: "input"
id: "reproduction"
attributes:
label: "Link to Reproduction"
description: |
A link to a env reproduction which demonstrates the bug (see
https://github.com/accezar/multi-package-start/#codesandbox-templates for
templates)
placeholder: "https://codesandbox.io/"
validations:
required: true
- type: "textarea"
id: "steps"
attributes:
label: "Steps to reproduce"
description: |
Explain how to cause the issue in the provided reproduction.
value: |
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error
- type: "input"
id: "lib-version"
attributes:
label: "Library Version"
description: "The version of lib you use."
placeholder: "0.0.0"
validations:
required: true
- type: "input"
id: "browser"
attributes:
label: "Browser"
description: "The browser(s) this issue occurred with."
placeholder: "Google Chrome 93"
- type: "checkboxes"
id: "operating-system"
attributes:
label: "Operating System"
description: "The operating system(s) this issue occurred with."
options:
- label: "macOS"
- label: "Windows"
- label: "Linux"
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
Use this section to provide any additional information you might have
like screenshots, notes, or links to ideas.
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: false
28 changes: 0 additions & 28 deletions .github/ISSUE_TEMPLATE/documentation-request.md

This file was deleted.

25 changes: 25 additions & 0 deletions .github/ISSUE_TEMPLATE/documentation_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: Documentation Request
about: Request for documentation to be added/altered
title: "doc - [component] - request title"
labels: "documentation request"
assignees: ""
---

## Thanks for filing a documentation request 📚!

If you have an idea for a new documentation topic, noticed that something is not properly documented, or feel that something is incorrect with the current documentation, you're in the right place!

#### 1. Subject:

What is the subject (component, function, topic) of this request?

> Ex: RadioGroup
---

#### 2. Description:

What about the subject's documentation should be added or changed?

> Ex: Add a usage example of RadioGroup in action
28 changes: 28 additions & 0 deletions .github/ISSUE_TEMPLATE/documentation_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
name: "Documentation Request"
description: "Request for documentation to be added/altered"
labels: ["needs triage", "Topic: Documentation 📚"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing a documentation request 📚!
If you have an idea for a new documentation topic, noticed that
something is not properly documented, or feel that something is
incorrect with the current documentation, you're in the right place!
- type: "input"
id: "subject"
attributes:
label: "Subject"
description: "What is the subject (component, function, topic) of this request?"
placeholder: "RadioGroup"
validations:
required: true
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "What about the subject's documentation should be added or changed?"
placeholder: "Add a usage example of RadioGroup in action"
validations:
required: true
43 changes: 26 additions & 17 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -1,42 +1,51 @@
---
name: Feature request
about: Request a new feature or improvement
title: feat - [component/context] - request title
labels: enhancement
assignees: ''
name: Feature Request
about: Request a feature or enhancement
title: "feat - [component/context] - feature request title"
labels: "feature requested"
assignees: ""
---

<!-- ## Thank you for creating a request 😄!
## Thanks for filing an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
-->
Please search open/closed issues before submitting. Someone might have asked the same thing before 😉!

#### 1. Description:

> Describe your request in one or two sentences:
Please describe your request in one or two sentences:

> ...
---

#### 2. Problem/Justification of Request:
#### 2. Problem Statement/Justification:

Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> Please describe the reason for this request to be added or changed. If it's related to a problem, please describe it as well.
> ...
---

#### 3. Proposed Solution:
#### 3. Proposed Solution or AP:

> Describe your idea for a solution to the problem.
Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> ...
---

#### 4. Alternatives:

> What other alternatives were considered before ordering this feature?
What alternative solutions have you considered before making this request?

> ...
---

#### 5. Additional Information:

> Information, details or resources (links, screenshots, etc.) that will facilitate this task.
What resources (links, screenshots, etc.) do you have to assist this effort?

> ...
51 changes: 51 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
name: "Feature Request"
description: "Request a feature or enhancement"
labels: ["needs triage"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "Please describe your request in one or two sentences."
validations:
required: true
- type: "textarea"
id: "justification"
attributes:
label: "Problem Statement/Justification"
description: |
Please provide valid reason(s) why this should be added
If this feature is related to a problem you've noticed, mention it as
well.
validations:
required: true
- type: "textarea"
id: "proposed-solution"
attributes:
label: "Proposed Solution or API"
description: |
Please provide code snippets, gists, or links to the ideal
design or API.
validations:
required: true
- type: "textarea"
id: "alternatives"
attributes:
label: "Alternatives"
description: |
What alternative solutions have you considered before making this
request?
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
What resources (links, screenshots, etc.) do you have to assist this
effort?
28 changes: 26 additions & 2 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -16,6 +16,28 @@ Please read the following points before requesting your Pull Request:
Describe your changes briefly and objectively.
<< Add here Pull Request. >>

### Current behavior

> Please describe the current behavior that you are modifying
<< Currently the component does... >>

### New behavior

> Please describe the behavior or changes this PR adds
>
- Change one here..
- Change two here..
- Change three here..


### Is this a breaking change (Yes/No):

> If Yes, please describe the impact and migration steps for existing users.
### Additional Information
<< Add here any additional info or N/A. >>

## Task

This Pull Request is associated with the following tasks in Jira:
@@ -27,8 +49,10 @@ This Pull Request is associated with the following tasks in Jira:
* Bar
* Baz

## Checklist


## Checklist
- [ ] Have you written tests for your changes?
- [ ] Have you successfully ran tests with your changes locally?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you updated the component documentation with the changes?
50 changes: 50 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

- Describe what will be added
- ...
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...

78 changes: 78 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and our
community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and
expression, level of experience, education, socio-economic status, 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 **architect-team@madeiramadeira.com.br**. 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
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
19 changes: 19 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Contributing

When contributing to this repository, please first discuss the change you wish to make via
[discussion](https://github.com/), issue, email, or any other method with the owners of this
repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull Request Process

1. Ensure that you follow the patterns to style and structure the component that we defined. Ensure
that all your work is sync with the latest versions.
2. Update the CHANGELOG.md with details of changes to the project, this includes new environment
variables, documentation change, new functionality and usefull information to identify any
possible breaking change.
3. Increase the version numbers of the package the new version that this Pull Request would
represent. The versioning scheme we use is [SemVer](http://semver.org/).
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.
20 changes: 20 additions & 0 deletions LICENSE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
Copyright (c) 2012-2022 MadeiraMadeira

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
20 changes: 12 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
@@ -63,19 +63,23 @@ Example of the workflow to create the environment.
## Single project examples

You can find light examples:
* [Lambda API Light](./examples/lambda_api_light)
* [Lambda CRON Light](./examples/lambda_cron_light)

[//]: # (* [Lambda API Light]&#40;./examples/lambda_api_light&#41;)
[//]: # (* [Lambda CRON Light]&#40;./examples/lambda_cron_light&#41;)
* [Lambda SQS Light](./examples/lambda_sqs_light)
* [Lambda SNS Light](./examples/lambda_sns_light)
* [Lambda S3 Light](./examples/lambda_s3_light)
*

[//]: # (* [Lambda SNS Light]&#40;./examples/lambda_sns_light&#41;)
[//]: # (* [Lambda S3 Light]&#40;./examples/lambda_s3_light&#41;)

You can find complex examples:
* [Lambda API](./examples/lambda_api)
* [Lambda API RESTful](./examples/lambda_api_restful)
* [Lambda CRON](./examples/lambda_cron)

[//]: # (* [Lambda CRON]&#40;./examples/lambda_cron&#41;)
* [Lambda SQS](./examples/lambda_sqs)
* [Lambda SNS](./examples/lambda_sns)
* [Lambda S3](./examples/lambda_s3)

[//]: # (* [Lambda SNS]&#40;./examples/lambda_sns&#41;)
[//]: # (* [Lambda S3]&#40;./examples/lambda_s3&#41;)

## Details about requirements files
### requirements.txt
60 changes: 41 additions & 19 deletions examples/lambda_api/.github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,45 +1,67 @@
---
name: Bug reports
about: Bug reports
title: bug - [component/module] - bug title
labels: ''
assignees: ''
name: Bug Report
about: File a bug report
title: "bug - [component/module] - bug title"
labels: "bug report"
assignees: ""
---

<!-- ## We appreciate you creating a new issue 😄!
## Thanks for creating an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
Please search open/closed issues before submitting. Someone might have asked the same thing before.
To help us, please take the time to accurately fill out this template. ❤️

-->
#### 1. Describe the bug:

#### 1. Bug description:
> A brief description of the issue.
> Ex: When I \_**\_, I expected \_\_** to happen but \_\_\_\_ happened instead.
> Enter a simple description about the bug
> Example: When I \_**\_, I expected the behavior \_\_** but the behavior \_\_\_\_ occurred
---

#### 2. Version:

> The version of this library that are using.
---

#### 3. Link to bug example:
#### 3. Link to Reproduction:

> Link to CodeSandbox or any sandbox service that shows the error happening (see https://github.com/accezar/multi-package-start#codesandbox-templates for examples)
> A link to a CodeSandbox or any other sandbox service which demonstrates the bug (see https://github.com/accezar/multi-package-start#codesandbox-templates for templates)
---

#### 4. Step-by-step to reproduces the error behavior:
#### 4. Steps to reproduce

> 1. Go to '...'
> 2. Click on '....'
> 3. Get the error
> 3. Scroll down to '....'
> 4. See error
---

#### 5. Screenshots

> Se possível, adicione screenshots para ajudar a explicar o erro
> If applicable, add screenshots to help explain your problem.
---

#### 6. Desktop (please complete the following information):

- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

---

#### 7. Smartphone (please complete the following information):

- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

---

#### 6. Extra info
#### 8. Additional context

> Add any additional information here that you think is relevant to understanding the issue
> Add any other context about the problem here.
75 changes: 75 additions & 0 deletions examples/lambda_api/.github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
name: "Bug Report"
description: "File a bug report"
labels: ["bug report"]
body:
- type: "markdown"
attributes:
value: |
Thanks for creating an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
We're all volunteers here, so help us help you by taking the time to
accurately fill out this template. ❤️
- type: "input"
id: "description"
attributes:
label: "Description"
description: "A brief description of the issue."
placeholder: |
When I ____, I expected ____ to happen but ____ happened instead.
validations:
required: true
- type: "input"
id: "reproduction"
attributes:
label: "Link to Reproduction"
description: |
A link to a env reproduction which demonstrates the bug (see
https://github.com/accezar/multi-package-start/#codesandbox-templates for
templates)
placeholder: "https://codesandbox.io/"
validations:
required: true
- type: "textarea"
id: "steps"
attributes:
label: "Steps to reproduce"
description: |
Explain how to cause the issue in the provided reproduction.
value: |
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error
- type: "input"
id: "lib-version"
attributes:
label: "Library Version"
description: "The version of lib you use."
placeholder: "0.0.0"
validations:
required: true
- type: "input"
id: "browser"
attributes:
label: "Browser"
description: "The browser(s) this issue occurred with."
placeholder: "Google Chrome 93"
- type: "checkboxes"
id: "operating-system"
attributes:
label: "Operating System"
description: "The operating system(s) this issue occurred with."
options:
- label: "macOS"
- label: "Windows"
- label: "Linux"
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
Use this section to provide any additional information you might have
like screenshots, notes, or links to ideas.
1 change: 1 addition & 0 deletions examples/lambda_api/.github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: false

This file was deleted.

Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: Documentation Request
about: Request for documentation to be added/altered
title: "doc - [component] - request title"
labels: "documentation request"
assignees: ""
---

## Thanks for filing a documentation request 📚!

If you have an idea for a new documentation topic, noticed that something is not properly documented, or feel that something is incorrect with the current documentation, you're in the right place!

#### 1. Subject:

What is the subject (component, function, topic) of this request?

> Ex: RadioGroup
---

#### 2. Description:

What about the subject's documentation should be added or changed?

> Ex: Add a usage example of RadioGroup in action
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
name: "Documentation Request"
description: "Request for documentation to be added/altered"
labels: ["needs triage", "Topic: Documentation 📚"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing a documentation request 📚!
If you have an idea for a new documentation topic, noticed that
something is not properly documented, or feel that something is
incorrect with the current documentation, you're in the right place!
- type: "input"
id: "subject"
attributes:
label: "Subject"
description: "What is the subject (component, function, topic) of this request?"
placeholder: "RadioGroup"
validations:
required: true
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "What about the subject's documentation should be added or changed?"
placeholder: "Add a usage example of RadioGroup in action"
validations:
required: true
43 changes: 26 additions & 17 deletions examples/lambda_api/.github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -1,42 +1,51 @@
---
name: Feature request
about: Request a new feature or improvement
title: feat - [component/context] - request title
labels: enhancement
assignees: ''
name: Feature Request
about: Request a feature or enhancement
title: "feat - [component/context] - feature request title"
labels: "feature requested"
assignees: ""
---

<!-- ## Thank you for creating a request 😄!
## Thanks for filing an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
-->
Please search open/closed issues before submitting. Someone might have asked the same thing before 😉!

#### 1. Description:

> Describe your request in one or two sentences:
Please describe your request in one or two sentences:

> ...
---

#### 2. Problem/Justification of Request:
#### 2. Problem Statement/Justification:

Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> Please describe the reason for this request to be added or changed. If it's related to a problem, please describe it as well.
> ...
---

#### 3. Proposed Solution:
#### 3. Proposed Solution or AP:

> Describe your idea for a solution to the problem.
Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> ...
---

#### 4. Alternatives:

> What other alternatives were considered before ordering this feature?
What alternative solutions have you considered before making this request?

> ...
---

#### 5. Additional Information:

> Information, details or resources (links, screenshots, etc.) that will facilitate this task.
What resources (links, screenshots, etc.) do you have to assist this effort?

> ...
51 changes: 51 additions & 0 deletions examples/lambda_api/.github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
name: "Feature Request"
description: "Request a feature or enhancement"
labels: ["needs triage"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "Please describe your request in one or two sentences."
validations:
required: true
- type: "textarea"
id: "justification"
attributes:
label: "Problem Statement/Justification"
description: |
Please provide valid reason(s) why this should be added
If this feature is related to a problem you've noticed, mention it as
well.
validations:
required: true
- type: "textarea"
id: "proposed-solution"
attributes:
label: "Proposed Solution or API"
description: |
Please provide code snippets, gists, or links to the ideal
design or API.
validations:
required: true
- type: "textarea"
id: "alternatives"
attributes:
label: "Alternatives"
description: |
What alternative solutions have you considered before making this
request?
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
What resources (links, screenshots, etc.) do you have to assist this
effort?
28 changes: 26 additions & 2 deletions examples/lambda_api/.github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -16,6 +16,28 @@ Please read the following points before requesting your Pull Request:
Describe your changes briefly and objectively.
<< Add here Pull Request. >>

### Current behavior

> Please describe the current behavior that you are modifying
<< Currently the component does... >>

### New behavior

> Please describe the behavior or changes this PR adds
>
- Change one here..
- Change two here..
- Change three here..


### Is this a breaking change (Yes/No):

> If Yes, please describe the impact and migration steps for existing users.
### Additional Information
<< Add here any additional info or N/A. >>

## Task

This Pull Request is associated with the following tasks in Jira:
@@ -27,8 +49,10 @@ This Pull Request is associated with the following tasks in Jira:
* Bar
* Baz

## Checklist


## Checklist
- [ ] Have you written tests for your changes?
- [ ] Have you successfully ran tests with your changes locally?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you updated the component documentation with the changes?
52 changes: 49 additions & 3 deletions examples/lambda_api/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,50 @@
# template-serverless-lambda-python - Lambda API - Changelog
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

- Describe what will be added
- ...
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...

## v1.0.0
* First version of the project;
72 changes: 52 additions & 20 deletions examples/lambda_api/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -2,45 +2,77 @@

## 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.
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and our
community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and
expression, level of experience, education, socio-economic status, nationality,
personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:
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
- 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
- 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 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.
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.
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 james@alt-three.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.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at **architect-team@madeiramadeira.com.br**. 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.
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]
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 1.4, available at
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
19 changes: 19 additions & 0 deletions examples/lambda_api/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Contributing

When contributing to this repository, please first discuss the change you wish to make via
[discussion](https://github.com/), issue, email, or any other method with the owners of this
repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull Request Process

1. Ensure that you follow the patterns to style and structure the component that we defined. Ensure
that all your work is sync with the latest versions.
2. Update the CHANGELOG.md with details of changes to the project, this includes new environment
variables, documentation change, new functionality and usefull information to identify any
possible breaking change.
3. Increase the version numbers of the package the new version that this Pull Request would
represent. The versioning scheme we use is [SemVer](http://semver.org/).
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.
60 changes: 41 additions & 19 deletions examples/lambda_api_restful/.github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,45 +1,67 @@
---
name: Bug reports
about: Bug reports
title: bug - [component/module] - bug title
labels: ''
assignees: ''
name: Bug Report
about: File a bug report
title: "bug - [component/module] - bug title"
labels: "bug report"
assignees: ""
---

<!-- ## We appreciate you creating a new issue 😄!
## Thanks for creating an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
Please search open/closed issues before submitting. Someone might have asked the same thing before.
To help us, please take the time to accurately fill out this template. ❤️

-->
#### 1. Describe the bug:

#### 1. Bug description:
> A brief description of the issue.
> Ex: When I \_**\_, I expected \_\_** to happen but \_\_\_\_ happened instead.
> Enter a simple description about the bug
> Example: When I \_**\_, I expected the behavior \_\_** but the behavior \_\_\_\_ occurred
---

#### 2. Version:

> The version of this library that are using.
---

#### 3. Link to bug example:
#### 3. Link to Reproduction:

> Link to CodeSandbox or any sandbox service that shows the error happening (see https://github.com/accezar/multi-package-start#codesandbox-templates for examples)
> A link to a CodeSandbox or any other sandbox service which demonstrates the bug (see https://github.com/accezar/multi-package-start#codesandbox-templates for templates)
---

#### 4. Step-by-step to reproduces the error behavior:
#### 4. Steps to reproduce

> 1. Go to '...'
> 2. Click on '....'
> 3. Get the error
> 3. Scroll down to '....'
> 4. See error
---

#### 5. Screenshots

> Se possível, adicione screenshots para ajudar a explicar o erro
> If applicable, add screenshots to help explain your problem.
---

#### 6. Desktop (please complete the following information):

- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

---

#### 7. Smartphone (please complete the following information):

- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

---

#### 6. Extra info
#### 8. Additional context

> Add any additional information here that you think is relevant to understanding the issue
> Add any other context about the problem here.
75 changes: 75 additions & 0 deletions examples/lambda_api_restful/.github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
name: "Bug Report"
description: "File a bug report"
labels: ["bug report"]
body:
- type: "markdown"
attributes:
value: |
Thanks for creating an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
We're all volunteers here, so help us help you by taking the time to
accurately fill out this template. ❤️
- type: "input"
id: "description"
attributes:
label: "Description"
description: "A brief description of the issue."
placeholder: |
When I ____, I expected ____ to happen but ____ happened instead.
validations:
required: true
- type: "input"
id: "reproduction"
attributes:
label: "Link to Reproduction"
description: |
A link to a env reproduction which demonstrates the bug (see
https://github.com/accezar/multi-package-start/#codesandbox-templates for
templates)
placeholder: "https://codesandbox.io/"
validations:
required: true
- type: "textarea"
id: "steps"
attributes:
label: "Steps to reproduce"
description: |
Explain how to cause the issue in the provided reproduction.
value: |
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error
- type: "input"
id: "lib-version"
attributes:
label: "Library Version"
description: "The version of lib you use."
placeholder: "0.0.0"
validations:
required: true
- type: "input"
id: "browser"
attributes:
label: "Browser"
description: "The browser(s) this issue occurred with."
placeholder: "Google Chrome 93"
- type: "checkboxes"
id: "operating-system"
attributes:
label: "Operating System"
description: "The operating system(s) this issue occurred with."
options:
- label: "macOS"
- label: "Windows"
- label: "Linux"
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
Use this section to provide any additional information you might have
like screenshots, notes, or links to ideas.
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: false

This file was deleted.

Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: Documentation Request
about: Request for documentation to be added/altered
title: "doc - [component] - request title"
labels: "documentation request"
assignees: ""
---

## Thanks for filing a documentation request 📚!

If you have an idea for a new documentation topic, noticed that something is not properly documented, or feel that something is incorrect with the current documentation, you're in the right place!

#### 1. Subject:

What is the subject (component, function, topic) of this request?

> Ex: RadioGroup
---

#### 2. Description:

What about the subject's documentation should be added or changed?

> Ex: Add a usage example of RadioGroup in action
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
name: "Documentation Request"
description: "Request for documentation to be added/altered"
labels: ["needs triage", "Topic: Documentation 📚"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing a documentation request 📚!
If you have an idea for a new documentation topic, noticed that
something is not properly documented, or feel that something is
incorrect with the current documentation, you're in the right place!
- type: "input"
id: "subject"
attributes:
label: "Subject"
description: "What is the subject (component, function, topic) of this request?"
placeholder: "RadioGroup"
validations:
required: true
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "What about the subject's documentation should be added or changed?"
placeholder: "Add a usage example of RadioGroup in action"
validations:
required: true
Original file line number Diff line number Diff line change
@@ -1,42 +1,51 @@
---
name: Feature request
about: Request a new feature or improvement
title: feat - [component/context] - request title
labels: enhancement
assignees: ''
name: Feature Request
about: Request a feature or enhancement
title: "feat - [component/context] - feature request title"
labels: "feature requested"
assignees: ""
---

<!-- ## Thank you for creating a request 😄!
## Thanks for filing an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
-->
Please search open/closed issues before submitting. Someone might have asked the same thing before 😉!

#### 1. Description:

> Describe your request in one or two sentences:
Please describe your request in one or two sentences:

> ...
---

#### 2. Problem/Justification of Request:
#### 2. Problem Statement/Justification:

Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> Please describe the reason for this request to be added or changed. If it's related to a problem, please describe it as well.
> ...
---

#### 3. Proposed Solution:
#### 3. Proposed Solution or AP:

> Describe your idea for a solution to the problem.
Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> ...
---

#### 4. Alternatives:

> What other alternatives were considered before ordering this feature?
What alternative solutions have you considered before making this request?

> ...
---

#### 5. Additional Information:

> Information, details or resources (links, screenshots, etc.) that will facilitate this task.
What resources (links, screenshots, etc.) do you have to assist this effort?

> ...
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
name: "Feature Request"
description: "Request a feature or enhancement"
labels: ["needs triage"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "Please describe your request in one or two sentences."
validations:
required: true
- type: "textarea"
id: "justification"
attributes:
label: "Problem Statement/Justification"
description: |
Please provide valid reason(s) why this should be added
If this feature is related to a problem you've noticed, mention it as
well.
validations:
required: true
- type: "textarea"
id: "proposed-solution"
attributes:
label: "Proposed Solution or API"
description: |
Please provide code snippets, gists, or links to the ideal
design or API.
validations:
required: true
- type: "textarea"
id: "alternatives"
attributes:
label: "Alternatives"
description: |
What alternative solutions have you considered before making this
request?
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
What resources (links, screenshots, etc.) do you have to assist this
effort?
28 changes: 26 additions & 2 deletions examples/lambda_api_restful/.github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -16,6 +16,28 @@ Please read the following points before requesting your Pull Request:
Describe your changes briefly and objectively.
<< Add here Pull Request. >>

### Current behavior

> Please describe the current behavior that you are modifying
<< Currently the component does... >>

### New behavior

> Please describe the behavior or changes this PR adds
>
- Change one here..
- Change two here..
- Change three here..


### Is this a breaking change (Yes/No):

> If Yes, please describe the impact and migration steps for existing users.
### Additional Information
<< Add here any additional info or N/A. >>

## Task

This Pull Request is associated with the following tasks in Jira:
@@ -27,8 +49,10 @@ This Pull Request is associated with the following tasks in Jira:
* Bar
* Baz

## Checklist


## Checklist
- [ ] Have you written tests for your changes?
- [ ] Have you successfully ran tests with your changes locally?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you updated the component documentation with the changes?
52 changes: 49 additions & 3 deletions examples/lambda_api_restful/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,50 @@
# template-serverless-lambda-python - Lambda API - Changelog
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

- Describe what will be added
- ...
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...

## v1.0.0
* First version of the project;
72 changes: 52 additions & 20 deletions examples/lambda_api_restful/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -2,45 +2,77 @@

## 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.
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and our
community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and
expression, level of experience, education, socio-economic status, nationality,
personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:
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
- 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
- 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 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.
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.
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 james@alt-three.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.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at **architect-team@madeiramadeira.com.br**. 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.
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]
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 1.4, available at
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
19 changes: 19 additions & 0 deletions examples/lambda_api_restful/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Contributing

When contributing to this repository, please first discuss the change you wish to make via
[discussion](https://github.com/), issue, email, or any other method with the owners of this
repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull Request Process

1. Ensure that you follow the patterns to style and structure the component that we defined. Ensure
that all your work is sync with the latest versions.
2. Update the CHANGELOG.md with details of changes to the project, this includes new environment
variables, documentation change, new functionality and usefull information to identify any
possible breaking change.
3. Increase the version numbers of the package the new version that this Pull Request would
represent. The versioning scheme we use is [SemVer](http://semver.org/).
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.
60 changes: 41 additions & 19 deletions examples/lambda_sqs/.github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,45 +1,67 @@
---
name: Bug reports
about: Bug reports
title: bug - [component/module] - bug title
labels: ''
assignees: ''
name: Bug Report
about: File a bug report
title: "bug - [component/module] - bug title"
labels: "bug report"
assignees: ""
---

<!-- ## We appreciate you creating a new issue 😄!
## Thanks for creating an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
Please search open/closed issues before submitting. Someone might have asked the same thing before.
To help us, please take the time to accurately fill out this template. ❤️

-->
#### 1. Describe the bug:

#### 1. Bug description:
> A brief description of the issue.
> Ex: When I \_**\_, I expected \_\_** to happen but \_\_\_\_ happened instead.
> Enter a simple description about the bug
> Example: When I \_**\_, I expected the behavior \_\_** but the behavior \_\_\_\_ occurred
---

#### 2. Version:

> The version of this library that are using.
---

#### 3. Link to bug example:
#### 3. Link to Reproduction:

> Link to CodeSandbox or any sandbox service that shows the error happening (see https://github.com/accezar/multi-package-start#codesandbox-templates for examples)
> A link to a CodeSandbox or any other sandbox service which demonstrates the bug (see https://github.com/accezar/multi-package-start#codesandbox-templates for templates)
---

#### 4. Step-by-step to reproduces the error behavior:
#### 4. Steps to reproduce

> 1. Go to '...'
> 2. Click on '....'
> 3. Get the error
> 3. Scroll down to '....'
> 4. See error
---

#### 5. Screenshots

> Se possível, adicione screenshots para ajudar a explicar o erro
> If applicable, add screenshots to help explain your problem.
---

#### 6. Desktop (please complete the following information):

- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

---

#### 7. Smartphone (please complete the following information):

- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

---

#### 6. Extra info
#### 8. Additional context

> Add any additional information here that you think is relevant to understanding the issue
> Add any other context about the problem here.
75 changes: 75 additions & 0 deletions examples/lambda_sqs/.github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
name: "Bug Report"
description: "File a bug report"
labels: ["bug report"]
body:
- type: "markdown"
attributes:
value: |
Thanks for creating an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
We're all volunteers here, so help us help you by taking the time to
accurately fill out this template. ❤️
- type: "input"
id: "description"
attributes:
label: "Description"
description: "A brief description of the issue."
placeholder: |
When I ____, I expected ____ to happen but ____ happened instead.
validations:
required: true
- type: "input"
id: "reproduction"
attributes:
label: "Link to Reproduction"
description: |
A link to a env reproduction which demonstrates the bug (see
https://github.com/accezar/multi-package-start/#codesandbox-templates for
templates)
placeholder: "https://codesandbox.io/"
validations:
required: true
- type: "textarea"
id: "steps"
attributes:
label: "Steps to reproduce"
description: |
Explain how to cause the issue in the provided reproduction.
value: |
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error
- type: "input"
id: "lib-version"
attributes:
label: "Library Version"
description: "The version of lib you use."
placeholder: "0.0.0"
validations:
required: true
- type: "input"
id: "browser"
attributes:
label: "Browser"
description: "The browser(s) this issue occurred with."
placeholder: "Google Chrome 93"
- type: "checkboxes"
id: "operating-system"
attributes:
label: "Operating System"
description: "The operating system(s) this issue occurred with."
options:
- label: "macOS"
- label: "Windows"
- label: "Linux"
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
Use this section to provide any additional information you might have
like screenshots, notes, or links to ideas.
1 change: 1 addition & 0 deletions examples/lambda_sqs/.github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: false

This file was deleted.

Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: Documentation Request
about: Request for documentation to be added/altered
title: "doc - [component] - request title"
labels: "documentation request"
assignees: ""
---

## Thanks for filing a documentation request 📚!

If you have an idea for a new documentation topic, noticed that something is not properly documented, or feel that something is incorrect with the current documentation, you're in the right place!

#### 1. Subject:

What is the subject (component, function, topic) of this request?

> Ex: RadioGroup
---

#### 2. Description:

What about the subject's documentation should be added or changed?

> Ex: Add a usage example of RadioGroup in action
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
name: "Documentation Request"
description: "Request for documentation to be added/altered"
labels: ["needs triage", "Topic: Documentation 📚"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing a documentation request 📚!
If you have an idea for a new documentation topic, noticed that
something is not properly documented, or feel that something is
incorrect with the current documentation, you're in the right place!
- type: "input"
id: "subject"
attributes:
label: "Subject"
description: "What is the subject (component, function, topic) of this request?"
placeholder: "RadioGroup"
validations:
required: true
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "What about the subject's documentation should be added or changed?"
placeholder: "Add a usage example of RadioGroup in action"
validations:
required: true
43 changes: 26 additions & 17 deletions examples/lambda_sqs/.github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -1,42 +1,51 @@
---
name: Feature request
about: Request a new feature or improvement
title: feat - [component/context] - request title
labels: enhancement
assignees: ''
name: Feature Request
about: Request a feature or enhancement
title: "feat - [component/context] - feature request title"
labels: "feature requested"
assignees: ""
---

<!-- ## Thank you for creating a request 😄!
## Thanks for filing an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
-->
Please search open/closed issues before submitting. Someone might have asked the same thing before 😉!

#### 1. Description:

> Describe your request in one or two sentences:
Please describe your request in one or two sentences:

> ...
---

#### 2. Problem/Justification of Request:
#### 2. Problem Statement/Justification:

Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> Please describe the reason for this request to be added or changed. If it's related to a problem, please describe it as well.
> ...
---

#### 3. Proposed Solution:
#### 3. Proposed Solution or AP:

> Describe your idea for a solution to the problem.
Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> ...
---

#### 4. Alternatives:

> What other alternatives were considered before ordering this feature?
What alternative solutions have you considered before making this request?

> ...
---

#### 5. Additional Information:

> Information, details or resources (links, screenshots, etc.) that will facilitate this task.
What resources (links, screenshots, etc.) do you have to assist this effort?

> ...
51 changes: 51 additions & 0 deletions examples/lambda_sqs/.github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
name: "Feature Request"
description: "Request a feature or enhancement"
labels: ["needs triage"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "Please describe your request in one or two sentences."
validations:
required: true
- type: "textarea"
id: "justification"
attributes:
label: "Problem Statement/Justification"
description: |
Please provide valid reason(s) why this should be added
If this feature is related to a problem you've noticed, mention it as
well.
validations:
required: true
- type: "textarea"
id: "proposed-solution"
attributes:
label: "Proposed Solution or API"
description: |
Please provide code snippets, gists, or links to the ideal
design or API.
validations:
required: true
- type: "textarea"
id: "alternatives"
attributes:
label: "Alternatives"
description: |
What alternative solutions have you considered before making this
request?
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
What resources (links, screenshots, etc.) do you have to assist this
effort?
28 changes: 26 additions & 2 deletions examples/lambda_sqs/.github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -16,6 +16,28 @@ Please read the following points before requesting your Pull Request:
Describe your changes briefly and objectively.
<< Add here Pull Request. >>

### Current behavior

> Please describe the current behavior that you are modifying
<< Currently the component does... >>

### New behavior

> Please describe the behavior or changes this PR adds
>
- Change one here..
- Change two here..
- Change three here..


### Is this a breaking change (Yes/No):

> If Yes, please describe the impact and migration steps for existing users.
### Additional Information
<< Add here any additional info or N/A. >>

## Task

This Pull Request is associated with the following tasks in Jira:
@@ -27,8 +49,10 @@ This Pull Request is associated with the following tasks in Jira:
* Bar
* Baz

## Checklist


## Checklist
- [ ] Have you written tests for your changes?
- [ ] Have you successfully ran tests with your changes locally?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you updated the component documentation with the changes?
52 changes: 49 additions & 3 deletions examples/lambda_sqs/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,50 @@
# template-serverless-lambda-python - Lambda SQS - Changelog
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

- Describe what will be added
- ...
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...

## v1.0.0
* First version of the project;
72 changes: 52 additions & 20 deletions examples/lambda_sqs/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -2,45 +2,77 @@

## 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.
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and our
community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and
expression, level of experience, education, socio-economic status, nationality,
personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:
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
- 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
- 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 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.
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.
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 james@alt-three.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.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at **architect-team@madeiramadeira.com.br**. 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.
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]
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 1.4, available at
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
19 changes: 19 additions & 0 deletions examples/lambda_sqs/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Contributing

When contributing to this repository, please first discuss the change you wish to make via
[discussion](https://github.com/), issue, email, or any other method with the owners of this
repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull Request Process

1. Ensure that you follow the patterns to style and structure the component that we defined. Ensure
that all your work is sync with the latest versions.
2. Update the CHANGELOG.md with details of changes to the project, this includes new environment
variables, documentation change, new functionality and usefull information to identify any
possible breaking change.
3. Increase the version numbers of the package the new version that this Pull Request would
represent. The versioning scheme we use is [SemVer](http://semver.org/).
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.
60 changes: 41 additions & 19 deletions examples/lambda_sqs_light/.github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,45 +1,67 @@
---
name: Bug reports
about: Bug reports
title: bug - [component/module] - bug title
labels: ''
assignees: ''
name: Bug Report
about: File a bug report
title: "bug - [component/module] - bug title"
labels: "bug report"
assignees: ""
---

<!-- ## We appreciate you creating a new issue 😄!
## Thanks for creating an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
Please search open/closed issues before submitting. Someone might have asked the same thing before.
To help us, please take the time to accurately fill out this template. ❤️

-->
#### 1. Describe the bug:

#### 1. Bug description:
> A brief description of the issue.
> Ex: When I \_**\_, I expected \_\_** to happen but \_\_\_\_ happened instead.
> Enter a simple description about the bug
> Example: When I \_**\_, I expected the behavior \_\_** but the behavior \_\_\_\_ occurred
---

#### 2. Version:

> The version of this library that are using.
---

#### 3. Link to bug example:
#### 3. Link to Reproduction:

> Link to CodeSandbox or any sandbox service that shows the error happening (see https://github.com/accezar/multi-package-start#codesandbox-templates for examples)
> A link to a CodeSandbox or any other sandbox service which demonstrates the bug (see https://github.com/accezar/multi-package-start#codesandbox-templates for templates)
---

#### 4. Step-by-step to reproduces the error behavior:
#### 4. Steps to reproduce

> 1. Go to '...'
> 2. Click on '....'
> 3. Get the error
> 3. Scroll down to '....'
> 4. See error
---

#### 5. Screenshots

> Se possível, adicione screenshots para ajudar a explicar o erro
> If applicable, add screenshots to help explain your problem.
---

#### 6. Desktop (please complete the following information):

- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

---

#### 7. Smartphone (please complete the following information):

- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

---

#### 6. Extra info
#### 8. Additional context

> Add any additional information here that you think is relevant to understanding the issue
> Add any other context about the problem here.
75 changes: 75 additions & 0 deletions examples/lambda_sqs_light/.github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
name: "Bug Report"
description: "File a bug report"
labels: ["bug report"]
body:
- type: "markdown"
attributes:
value: |
Thanks for creating an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
We're all volunteers here, so help us help you by taking the time to
accurately fill out this template. ❤️
- type: "input"
id: "description"
attributes:
label: "Description"
description: "A brief description of the issue."
placeholder: |
When I ____, I expected ____ to happen but ____ happened instead.
validations:
required: true
- type: "input"
id: "reproduction"
attributes:
label: "Link to Reproduction"
description: |
A link to a env reproduction which demonstrates the bug (see
https://github.com/accezar/multi-package-start/#codesandbox-templates for
templates)
placeholder: "https://codesandbox.io/"
validations:
required: true
- type: "textarea"
id: "steps"
attributes:
label: "Steps to reproduce"
description: |
Explain how to cause the issue in the provided reproduction.
value: |
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error
- type: "input"
id: "lib-version"
attributes:
label: "Library Version"
description: "The version of lib you use."
placeholder: "0.0.0"
validations:
required: true
- type: "input"
id: "browser"
attributes:
label: "Browser"
description: "The browser(s) this issue occurred with."
placeholder: "Google Chrome 93"
- type: "checkboxes"
id: "operating-system"
attributes:
label: "Operating System"
description: "The operating system(s) this issue occurred with."
options:
- label: "macOS"
- label: "Windows"
- label: "Linux"
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
Use this section to provide any additional information you might have
like screenshots, notes, or links to ideas.
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: false

This file was deleted.

Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: Documentation Request
about: Request for documentation to be added/altered
title: "doc - [component] - request title"
labels: "documentation request"
assignees: ""
---

## Thanks for filing a documentation request 📚!

If you have an idea for a new documentation topic, noticed that something is not properly documented, or feel that something is incorrect with the current documentation, you're in the right place!

#### 1. Subject:

What is the subject (component, function, topic) of this request?

> Ex: RadioGroup
---

#### 2. Description:

What about the subject's documentation should be added or changed?

> Ex: Add a usage example of RadioGroup in action
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
name: "Documentation Request"
description: "Request for documentation to be added/altered"
labels: ["needs triage", "Topic: Documentation 📚"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing a documentation request 📚!
If you have an idea for a new documentation topic, noticed that
something is not properly documented, or feel that something is
incorrect with the current documentation, you're in the right place!
- type: "input"
id: "subject"
attributes:
label: "Subject"
description: "What is the subject (component, function, topic) of this request?"
placeholder: "RadioGroup"
validations:
required: true
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "What about the subject's documentation should be added or changed?"
placeholder: "Add a usage example of RadioGroup in action"
validations:
required: true
43 changes: 26 additions & 17 deletions examples/lambda_sqs_light/.github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -1,42 +1,51 @@
---
name: Feature request
about: Request a new feature or improvement
title: feat - [component/context] - request title
labels: enhancement
assignees: ''
name: Feature Request
about: Request a feature or enhancement
title: "feat - [component/context] - feature request title"
labels: "feature requested"
assignees: ""
---

<!-- ## Thank you for creating a request 😄!
## Thanks for filing an issue 😄!

Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
-->
Please search open/closed issues before submitting. Someone might have asked the same thing before 😉!

#### 1. Description:

> Describe your request in one or two sentences:
Please describe your request in one or two sentences:

> ...
---

#### 2. Problem/Justification of Request:
#### 2. Problem Statement/Justification:

Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> Please describe the reason for this request to be added or changed. If it's related to a problem, please describe it as well.
> ...
---

#### 3. Proposed Solution:
#### 3. Proposed Solution or AP:

> Describe your idea for a solution to the problem.
Please provide valid reason(s) why this should be added.
If this feature is related to a problem you've noticed, mention it as well.

> ...
---

#### 4. Alternatives:

> What other alternatives were considered before ordering this feature?
What alternative solutions have you considered before making this request?

> ...
---

#### 5. Additional Information:

> Information, details or resources (links, screenshots, etc.) that will facilitate this task.
What resources (links, screenshots, etc.) do you have to assist this effort?

> ...
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
name: "Feature Request"
description: "Request a feature or enhancement"
labels: ["needs triage"]
body:
- type: "markdown"
attributes:
value: |
Thanks for filing an issue 😄!
Please search open/closed issues before submitting. Someone
might have asked the same thing before 😉!
- type: "textarea"
id: "description"
attributes:
label: "Description"
description: "Please describe your request in one or two sentences."
validations:
required: true
- type: "textarea"
id: "justification"
attributes:
label: "Problem Statement/Justification"
description: |
Please provide valid reason(s) why this should be added
If this feature is related to a problem you've noticed, mention it as
well.
validations:
required: true
- type: "textarea"
id: "proposed-solution"
attributes:
label: "Proposed Solution or API"
description: |
Please provide code snippets, gists, or links to the ideal
design or API.
validations:
required: true
- type: "textarea"
id: "alternatives"
attributes:
label: "Alternatives"
description: |
What alternative solutions have you considered before making this
request?
- type: "textarea"
id: "additional-information"
attributes:
label: "Additional Information"
description: |
What resources (links, screenshots, etc.) do you have to assist this
effort?
28 changes: 26 additions & 2 deletions examples/lambda_sqs_light/.github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -16,6 +16,28 @@ Please read the following points before requesting your Pull Request:
Describe your changes briefly and objectively.
<< Add here Pull Request. >>

### Current behavior

> Please describe the current behavior that you are modifying
<< Currently the component does... >>

### New behavior

> Please describe the behavior or changes this PR adds
>
- Change one here..
- Change two here..
- Change three here..


### Is this a breaking change (Yes/No):

> If Yes, please describe the impact and migration steps for existing users.
### Additional Information
<< Add here any additional info or N/A. >>

## Task

This Pull Request is associated with the following tasks in Jira:
@@ -27,8 +49,10 @@ This Pull Request is associated with the following tasks in Jira:
* Bar
* Baz

## Checklist


## Checklist
- [ ] Have you written tests for your changes?
- [ ] Have you successfully ran tests with your changes locally?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you lint your code locally prior to submission?
- [ ] Have you updated the component documentation with the changes?
52 changes: 49 additions & 3 deletions examples/lambda_sqs_light/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,50 @@
# template-serverless-lambda-python - Lambda SQS - Changelog
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

- Describe what will be added
- ...
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...


---


## [x.x.x] - YYYY-MM-DD
### Added
- Describe what was added
- ...


### Changed
- Describe what was changed
- ...


### Removed
- Describe what was removed
- ...

## v1.0.0
* First version of the project;
72 changes: 52 additions & 20 deletions examples/lambda_sqs_light/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -2,45 +2,77 @@

## 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.
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and our
community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and
expression, level of experience, education, socio-economic status, nationality,
personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:
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
- 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
- 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 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.
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.
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 james@alt-three.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.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at **architect-team@madeiramadeira.com.br**. 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.
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]
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 1.4, available at
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
19 changes: 19 additions & 0 deletions examples/lambda_sqs_light/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Contributing

When contributing to this repository, please first discuss the change you wish to make via
[discussion](https://github.com/), issue, email, or any other method with the owners of this
repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull Request Process

1. Ensure that you follow the patterns to style and structure the component that we defined. Ensure
that all your work is sync with the latest versions.
2. Update the CHANGELOG.md with details of changes to the project, this includes new environment
variables, documentation change, new functionality and usefull information to identify any
possible breaking change.
3. Increase the version numbers of the package the new version that this Pull Request would
represent. The versioning scheme we use is [SemVer](http://semver.org/).
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.
Empty file added samples/.gitkeep
Empty file.

0 comments on commit 11a05f0

Please sign in to comment.