Skip to content

Commit

Permalink
Move sbt project to root dir.
Browse files Browse the repository at this point in the history
  • Loading branch information
mrdziuban committed Dec 10, 2024
1 parent e166a7b commit 3ae2e06
Show file tree
Hide file tree
Showing 28 changed files with 8 additions and 9 deletions.
1 change: 0 additions & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,4 +25,3 @@ jobs:

- name: sbt test
run: sbt test
working-directory: ./scalafix
16 changes: 8 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ object Sub extends Super {
}
```

See `def allowed` in [`scalafix/rules/.../StrictSubclassAccess.scala`](https://github.com/mblink/scalafix-rules/blob/main/scalafix/rules/src/main/scala/fix/StrictSubclassAccess.scala#L35-L72)
See `def allowed` in [`rules/.../StrictSubclassAccess.scala`](https://github.com/mblink/scalafix-rules/blob/main/rules/src/main/scala/fix/StrictSubclassAccess.scala#L35-L72)
for the full list of super/subclass access combinations that are allowed by the rule.

## Development
Expand All @@ -64,7 +64,7 @@ Clone the repository, `cd` into the `scalafix` directory, and start SBT:

```bash
git clone [email protected]:mblink/scalafix-rules.git
cd scalafix-rules/scalafix
cd scalafix-rules
sbt
```

Expand All @@ -78,8 +78,8 @@ with `tests/test`.
Each test must have two files:

```
scalafix/input/src/main/scala/fix/TestName.scala
scalafix/output/src/main/scala/fix/TestName.scala
input/src/main/scala/fix/TestName.scala
output/src/main/scala/fix/TestName.scala
```

The file in the `input` directory should list the scalafix rule to be tested in a comment at the top, and can contain
Expand All @@ -97,7 +97,7 @@ For an example of a lint-only rule, imagine one named `ExampleLintRule` that add
equal to the literal string `"example"`. The `input` and `output` files for its test might look like this:

```scala
// scalafix/input/src/main/scala/fix/ExampleLintRule.scala
// input/src/main/scala/fix/ExampleLintRule.scala
/*
rule = ExampleLintRule
*/
Expand All @@ -109,7 +109,7 @@ object ExampleLintRule {
Don't use the literal string "example" */
}

// scalafix/output/src/main/scala/fix/ExampleLintRule.scala
// output/src/main/scala/fix/ExampleLintRule.scala
package fix

object ExampleLintRule {
Expand All @@ -121,7 +121,7 @@ For an example of a rewrite rule, imagine one named `ExampleRewriteRule` that ch
`"foobar"`. The `input` and `output` files for its test might look like this:

```scala
// scalafix/input/src/main/scala/fix/ExampleRewriteRule.scala
// input/src/main/scala/fix/ExampleRewriteRule.scala
/*
rule = ExampleRewriteRule
*/
Expand All @@ -131,7 +131,7 @@ object ExampleRewriteRule {
val example = "example"
}

// scalafix/output/src/main/scala/fix/ExampleRewriteRule.scala
// output/src/main/scala/fix/ExampleRewriteRule.scala
package fix

object ExampleRewriteRule {
Expand Down
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 comments on commit 3ae2e06

Please sign in to comment.