Merge branch 'master' into it_for_coerce_dates

.codacy.yml

@@ -0,0 +1,8 @@
+---
+engines:
+ duplication:
+   enabled: true
+   exclude_paths:
+     - elide-core/src/test/java/com/yahoo/elide/graphql/*
+exclude_paths:
+  - elide-core/src/test/java/com/yahoo/elide/graphql/*

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,41 @@
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+<!--- Please use code blocks when pasting code or sections of plain text (like logs)
+```java
+```
+-->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+<!--- Please use code blocks when pasting code or sections of plain text (like logs)
+```java
+```
+-->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+<!--- Please provide any relevant log information --->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Elide version used:
+* Environment name and version (Java 1.8.0_152):
+* Operating System and version:
+* Link to your project:

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+Resolves #<issue number> (if appropriate)
+
+## Description
+<!--- Describe your changes in detail -->
+<!--- If suggesting a new feature or change, please discuss it in an issue first -->
+<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Screenshots (if appropriate):
+
+
+## License
+I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

.github/dependabot.yml

@@ -0,0 +1,21 @@
+version: 2
+updates:
+- package-ecosystem: maven
+  directory: "/"
+  schedule:
+    interval: weekly
+    time: "13:00"
+  open-pull-requests-limit: 10
+  ignore:
+  - dependency-name: org.hibernate.validator:hibernate-validator
+    versions:
+    - 7.0.0.Final
+  - dependency-name: com.graphql-java:graphql-java
+    versions:
+    - "16.1"
+  - dependency-name: org.glassfish.jersey.inject:jersey-hk2
+    versions:
+    - 3.0.0
+  - dependency-name: org.glassfish.jersey.containers:jersey-container-servlet
+    versions:
+    - 3.0.0

.gitignore

@@ -8,3 +8,13 @@ test-output/
 *.iml
 bin
 dependency-reduced-pom.xml
+*.jar
+*.class
+*tags
+**.swp
+.project
+*/.project
+*/*/.project
+*.factorypath
+*.vscode
+.DS_Store

CONTRIBUTING.md

@@ -1,12 +1,26 @@
-# How to Contribute
+# How to contribute
+First, thanks for taking the time to contribute to our project! There are many ways you can help out.
 
-When submitting a pull request (PR), please use the following guidelines:
+### Questions
+
+If you have a question that needs an answer, [create an issue](https://github.com/yahoo/elide/issues/new), and label it as a question.
+
+### Issues for bugs or feature requests
+
+If you encounter any bugs in the code, or want to request a new feature or enhancement, please [create an issue](https://github.com/yahoo/elide/issues/new) to report it. Kindly add a label to indicate what type of issue it is.
+
+### Contribute Code
+We welcome your pull requests for bug fixes. To implement something new, please create an issue first so we can discuss it together.
+
+***Creating a Pull Request***
+Please follow [best practices](https://github.com/trein/dev-best-practices/wiki/Git-Commit-Best-Practices) for creating git commits.  In addition: 
 
 - Make sure your code respects existing formatting conventions. In general, follow
   the same coding style as the code that you are modifying. If you are using
   IntelliJ, you can import our code style settings xml:
-  [elide-intellij-codestyle.xml](https://github.com/yahoo/elide/raw/master/elide-intellij-codestyle.xml).
-- Do add/update documentation appropriately for the change you are making.
+  [elide-intellij-codestyle.xml](https://github.com/yahoo/elide/raw/master/elide-intellij-codestyle.xml)
+  or [elide-eclipse.importorder](https://github.com/yahoo/elide/raw/master/elide-eclipse.importorder).
+- Do add/update [documentation](https://github.com/yahoo/elide-doc) appropriately for the change you are making.
 - Bugfixes should include a unit test or integration test reproducing the issue.
 - Do not use author tags/information in the code.
 - Always include license header on each file your create. See [this example](https://github.com/yahoo/elide/blob/master/elide-core/src/main/java/com/yahoo/elide/Elide.java)
@@ -16,3 +30,14 @@ When submitting a pull request (PR), please use the following guidelines:
   Each commit should compile on its own and ideally pass tests.
 - Keep formatting changes in separate commits to make code reviews easier and
   distinguish them from actual code changes.
+
+When your code is ready to be submitted, [submit a pull request](https://help.github.com/articles/creating-a-pull-request/) to begin the code review process.
+
+We only seek to accept code that you are authorized to contribute to the project. We have added a pull request template on our projects so that your contributions are made with the following confirmation: 
+
+> I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
+
+## Code of Conduct
+
+We encourage inclusive and professional interactions on our project. We welcome everyone to open an issue, improve the documentation, report bug or submit a pull request. By participating in this project, you agree to abide by the [Yahoo Code of Conduct](Code-Of-Conduct.md). If you feel there is a conduct issue related to this project, please raise it per the Code of Conduct process and we will address it.
+

Code-Of-Conduct.md

@@ -0,0 +1,54 @@
+# Yahoo Open Source Code of Conduct
+
+## Summary
+This Code of Conduct is our way to encourage good behavior and discourage bad behavior in our open source community. We invite participation from many people to bring different perspectives to support this project. We pledge to do our part to foster a welcoming and professional environment free of harassment. We expect participants to communicate professionally and thoughtfully during their involvement with this project. 
+
+Participants may lose their good standing by engaging in misconduct. For example: insulting, threatening, or conveying unwelcome sexual content. We ask participants who observe conduct issues to report the incident directly to the project's Response Team at [email protected]. Yahoo will assign a respondent to address the issue. We may remove harassers from this project. 
+
+This code does not replace the terms of service or acceptable use policies of the websites used to support this project. We acknowledge that participants may be subject to additional conduct terms based on their employment which may govern their online expressions.
+
+## Details
+This Code of Conduct makes our expectations of participants in this community explicit.
+* We forbid harassment and abusive speech within this community.
+* We request participants to report misconduct to the project’s Response Team.
+* We urge participants to refrain from using discussion forums to play out a fight.
+
+### Expected Behaviors
+We expect participants in this community to conduct themselves professionally. Since our primary mode of communication is text on an online forum (e.g. issues, pull requests, comments, emails, or chats) devoid of vocal tone, gestures, or other context that is often vital to understanding, it is important that participants are attentive to their interaction style.
+
+* **Assume positive intent.** We ask community members to assume positive intent on the part of other people’s communications. We may disagree on details, but we expect all suggestions to be supportive of the community goals.
+* **Respect participants.** We expect participants will occasionally disagree. Even if we reject an idea, we welcome everyone’s participation. Open Source projects are learning experiences. Ask, explore, challenge, and then respectfully assert if you agree or disagree. If your idea is rejected, be more persuasive not bitter.
+* **Welcoming to new members.** New members bring new perspectives. Some may raise questions that have been addressed before. Kindly point them to existing discussions. Everyone is new to every project once.
+* **Be kind to beginners.** Beginners use open source projects to get experience. They might not be talented coders yet, and projects should not accept poor quality code. But we were all beginners once, and we need to engage kindly.
+* **Consider your impact on others.** Your work will be used by others, and you depend on the work of others. We expect community members to be considerate and establish a balance their self-interest with communal interest.
+* **Use words carefully.** We may not understand intent when you say something ironic. Poe’s Law suggests that without an emoticon people will misinterpret sarcasm. We ask community members to communicate plainly.
+* **Leave with class.** When you wish to resign from participating in this project for any reason, you are free to fork the code and create a competitive project. Open Source explicitly allows this. Your exit should not be dramatic or bitter. 
+
+### Unacceptable Behaviors
+Participants remain in good standing when they do not engage in misconduct or harassment. To elaborate: 
+* **Don't be a bigot.** Calling out project members by their identity or background in a negative or insulting manner. This includes, but is not limited to, slurs or insinuations related to protected or suspect classes e.g. race, color, citizenship, national origin, political belief, religion, sexual orientation, gender identity and expression, age, size, culture, ethnicity, genetic features, language, profession, national minority statue, mental or physical ability.
+* **Don't insult.** Insulting remarks about a person’s lifestyle practices.
+* **Don't dox.** Revealing private information about other participants without explicit permission.
+* **Don't intimidate.** Threats of violence or intimidation of any project member.
+* **Don't creep.** Unwanted sexual attention or content unsuited for the subject of this project.
+* **Don't disrupt.** Sustained disruptions in a discussion.
+* **Let us help.** Refusal to assist the Response Team to resolve an issue in the community.
+
+We do not list all forms of harassment, nor imply some forms of harassment are not worthy of action. Any participant who *feels* harassed or *observes* harassment, should report the incident. Victim of harassment should not address grievances in the public forum, as this often intensifies the problem. Report it, and let us address it off-line.
+
+### Reporting Issues
+If you experience or witness misconduct, or have any other concerns about the conduct of members of this project, please report it by contacting our Response Team at [email protected] who will handle your report with discretion. Your report should include:
+* Your preferred contact information. We cannot process anonymous reports.
+* Names (real or usernames) of those involved in the incident.
+* Your account of what occurred, and if the incident is ongoing. Please provide links to or transcripts of the publicly available records (e.g. a mailing list archive or a public IRC logger), so that we can review it.
+* Any additional information that may be helpful to achieve resolution.
+
+After filing a report, a representative will contact you directly to review the incident and ask additional questions. If a member of the Yahoo Response Team is named in an incident report, that member will be recused from handling your incident. If the complaint originates from a member of the Response Team, it will be addressed by a different member of the Response Team. We will consider reports to be confidential for the purpose of protecting victims of abuse. 
+
+### Scope
+Yahoo will assign a Response Team member with admin rights on the project and legal rights on the project copyright. The Response Team is empowered to restrict some privileges to the project as needed. Since this project is governed by an open source license, any participant may fork the code under the terms of the project license. The Response Team’s goal is to preserve the project if possible, and will restrict or remove participation from those who disrupt the project. 
+
+This code does not replace the terms of service or acceptable use policies that are provided by the websites used to support this community. Nor does this code apply to communications or actions that take place outside of the context of this community. Many participants in this project are also subject to codes of conduct based on their employment. This code is a social-contract that informs participants of our social expectations. It is not a terms of service or legal contract.
+
+## License and Acknowledgment. 
+This text is shared under the [CC-BY-4.0 license](https://creativecommons.org/licenses/by/4.0/). This code is based on a study conducted by the [TODO Group](https://todogroup.org/) of many codes used in the open source community. If you have feedback about this code, contact our Response Team at the address listed above.