accessors

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Convert to multi-project build in preparation to adding new modules

See #304

    • -240
    • +0
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 260 more files in changeset.
Remove rootProject.buildFileName = ‘build.gradle.kts’ from tests

See #37

    • -1
    • +0
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 3 more files in changeset.
Add source dir of generated project accessors to script source path

Enables navigation to the sources and quick documentation access.

See #281

    • -20
    • +40
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 7 more files in changeset.
Integration test samples

See #345

    • -3
    • +4
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 31 more files in changeset.
Unify handling of JIT and AOT project accessors

This is the first step toward fixing #340.

Resolves #338

Resolves #339

    • -23
    • +18
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 27 more files in changeset.
Polish

- Normalise placement of `private`, `protected`, `internal` and

`inline` modifiers

    • -8
    • +16
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 41 more files in changeset.
Remove ProjectExtensionsTaskRegistrationAction, apply a plugin instead

That way, no need to check for .kts files presence.

Builds not using gsk won’t suffer the performance penalty anymore.

Builds using gsk will benefit a small performance gain.

See #320

    • -0
    • +16
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 4 more files in changeset.
Generate accessors properties

    • -3
    • +3
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 1 more file in changeset.
Generated extension accessor can configure DeferredConfigurable extensions

    • -0
    • +37
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 1 more file in changeset.
Put automatic generation of extension accessors behind feature flag

Due to the potential for build script compilation failures resulting

from unaccessible extension types or illegal extension names at the

moment, automatic accessors will only be generated if the project

property `org.gradle.script.lang.kotlin.accessors.auto` is set to

`"true"`.

See #235

    • -4
    • +24
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 7 more files in changeset.
Omit accessors for extensions with illegal names

See #235

  1. … 2 more files in changeset.
Accept unorthodox extension names

See #235

    • -3
    • +3
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 1 more file in changeset.
Prove accessors are regenerated whenever the set of plugins change

See #235

    • -3
    • +36
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 1 more file in changeset.
Automatically generate type-safe accessors for contributed extensions

See #235

    • -2
    • +37
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 1 more file in changeset.
Make generated accessors visible to KotlinBuildScriptModel clients

See #234

    • -1
    • +19
    ./ProjectSchemaAccessorsIntegrationTest.kt
  1. … 23 more files in changeset.
Move away from deprecated `ref.javaClass` to `ref::class.java`

See #264

  1. … 9 more files in changeset.
Generate accessors for project extensions during `buildSrc` build

See: #229, #230, #231, #232, #233

    • -0
    • +38
    ./GenerateProjectSchemaTest.kt
    • -0
    • +51
    ./KotlinTypeStringTest.kt
    • -0
    • +58
    ./ProjectSchemaAccessorsIntegrationTest.kt
    • -0
    • +108
    ./ProjectSchemaTest.kt
  1. … 17 more files in changeset.