Skip to content

Prepare for tooling API #188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 7, 2022
Merged

Prepare for tooling API #188

merged 4 commits into from
Aug 7, 2022

Conversation

ajoberstar
Copy link
Member

@ajoberstar ajoberstar commented Aug 7, 2022

Covers a number of small changes needed to support the tooling API library.

Related issues:

Contributor Checklist

  • Review Contributing Guidelines.
  • Commits contain discrete changes, messages include context about why the change was made and reference the relevant issues.
  • Commit messages should be prefixed with one of the following (these are used to determine the next version we release):
    • patch: if the change added no new functionality and is backwards compatible
    • minor: if the change added new functionality and is backwards compatible
    • major: if the change is not backwards compatible
    • chore: if the change doesn't affect plugin logic/behavior at all (and obviously still backwards compatible)
    • Any of these can optionally specify an area of the plugin they affected in parentheses (e.g. patch(clojurescript): )
      • build
      • docs
      • clojure
      • clojurescript
      • common
      • repl
  • Provide functional tests. (under clojurephant-plugin/src/compatTest)
  • Update documentation for user-facing changes. (under docs/)
  • Ensure all verification tasks pass locally. (./gradlew check)
  • Ensure CI builds pass on all Java versions. (watch the checks tab once the PR is opened)

TIP: If troubleshooting a CI failure, look for the build scan URL in the workflow run summary.

@ajoberstar ajoberstar self-assigned this Aug 7, 2022
This builds an EDN version of the Clojurephant model, for use by
Gradle's tooling API. The plan is to leverage this in the new
clojurephant-tooling library, which will provider ways to start various
tasks, e.g. clojurescript builds and repls.
There was a mistake in the new logic for putting source on the REPL
classpath, that meant a project using both Clojure and ClojureScript
plugins would only end up with one on the classpath.

This new behavior delays evaluation of which source to include and is
now safe for both plugins to be applied.
Only when we are sending the options over to the compiler should we
quote them. We don't want the EDN we send to the tooling API to
include the quote.
Provides more detail to the tooling API.
@ajoberstar ajoberstar merged commit 257e33a into main Aug 7, 2022
@ajoberstar ajoberstar deleted the model branch August 7, 2022 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant