Kotlin DSL scope control on external non-changeable classes (similar to @DslMarker)
I have lots of external classes (generated externally; not under my control), which do not come with a builder and which are rather cumbersome to create. However using apply it is rather easy to build them, e.g.:
SomeOfTheObjects().apply {
someProperty = SomeOtherComplexObject().apply {
someOtherProperty = "..."
}
}
Now I like the way it works with the receiver, but I would like to prevent that I can set someProperty within SomeOtherComplexObject. If the classes were under my control, it would suffice to put a @DslMarker on that class, but as they aren't, the only other way that came to my mind, was to use also instead without renaming the parameter, e.g.:
SomeOfTheObjects().also {
it.someProperty = SomeOtherComplexObject().also {
it.someOtherProperty = "..."
//it.someProperty will not work if SomeOtherComplexObject has no such property
}
}
While it works, it now has tons of it. in the code and I was wondering, whether it is possible to have some similar behaviour as with the @DslMarker in place.
What I tried is a mixture of the following:
@DslMarker
annotation class DemoMarker
@DemoMarker
inline fun <T> T.build(@DemoMarker builder : T.() -> Unit) = this.apply(builder)
"mixture", because I ended up putting the annotation everywhere, but this doesn't have any effect. If I put it on a class it works as expected. Did I miss something and it is actually possible somehow? Or does anyone have an appropriate workaround for this, besides using also?
kotlin
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
add a comment |
I have lots of external classes (generated externally; not under my control), which do not come with a builder and which are rather cumbersome to create. However using apply it is rather easy to build them, e.g.:
SomeOfTheObjects().apply {
someProperty = SomeOtherComplexObject().apply {
someOtherProperty = "..."
}
}
Now I like the way it works with the receiver, but I would like to prevent that I can set someProperty within SomeOtherComplexObject. If the classes were under my control, it would suffice to put a @DslMarker on that class, but as they aren't, the only other way that came to my mind, was to use also instead without renaming the parameter, e.g.:
SomeOfTheObjects().also {
it.someProperty = SomeOtherComplexObject().also {
it.someOtherProperty = "..."
//it.someProperty will not work if SomeOtherComplexObject has no such property
}
}
While it works, it now has tons of it. in the code and I was wondering, whether it is possible to have some similar behaviour as with the @DslMarker in place.
What I tried is a mixture of the following:
@DslMarker
annotation class DemoMarker
@DemoMarker
inline fun <T> T.build(@DemoMarker builder : T.() -> Unit) = this.apply(builder)
"mixture", because I ended up putting the annotation everywhere, but this doesn't have any effect. If I put it on a class it works as expected. Did I miss something and it is actually possible somehow? Or does anyone have an appropriate workaround for this, besides using also?
kotlin
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
Can you inherit from that third-party classes? Probably inherit and mark your classes with@DslMaker?
– madhead
Nov 16 '18 at 11:59
That would be possible, but there are about ~4k classes in there... they are obviously generated from a schema. Maybe I can get the schema from somewhere and then just generate the sources from scratch and add the annotation while generating :-) still I think the question stays valid... and I hope there is some other workaround for this :-)
– Roland
Nov 16 '18 at 12:04
add a comment |
I have lots of external classes (generated externally; not under my control), which do not come with a builder and which are rather cumbersome to create. However using apply it is rather easy to build them, e.g.:
SomeOfTheObjects().apply {
someProperty = SomeOtherComplexObject().apply {
someOtherProperty = "..."
}
}
Now I like the way it works with the receiver, but I would like to prevent that I can set someProperty within SomeOtherComplexObject. If the classes were under my control, it would suffice to put a @DslMarker on that class, but as they aren't, the only other way that came to my mind, was to use also instead without renaming the parameter, e.g.:
SomeOfTheObjects().also {
it.someProperty = SomeOtherComplexObject().also {
it.someOtherProperty = "..."
//it.someProperty will not work if SomeOtherComplexObject has no such property
}
}
While it works, it now has tons of it. in the code and I was wondering, whether it is possible to have some similar behaviour as with the @DslMarker in place.
What I tried is a mixture of the following:
@DslMarker
annotation class DemoMarker
@DemoMarker
inline fun <T> T.build(@DemoMarker builder : T.() -> Unit) = this.apply(builder)
"mixture", because I ended up putting the annotation everywhere, but this doesn't have any effect. If I put it on a class it works as expected. Did I miss something and it is actually possible somehow? Or does anyone have an appropriate workaround for this, besides using also?
kotlin
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
I have lots of external classes (generated externally; not under my control), which do not come with a builder and which are rather cumbersome to create. However using apply it is rather easy to build them, e.g.:
SomeOfTheObjects().apply {
someProperty = SomeOtherComplexObject().apply {
someOtherProperty = "..."
}
}
Now I like the way it works with the receiver, but I would like to prevent that I can set someProperty within SomeOtherComplexObject. If the classes were under my control, it would suffice to put a @DslMarker on that class, but as they aren't, the only other way that came to my mind, was to use also instead without renaming the parameter, e.g.:
SomeOfTheObjects().also {
it.someProperty = SomeOtherComplexObject().also {
it.someOtherProperty = "..."
//it.someProperty will not work if SomeOtherComplexObject has no such property
}
}
While it works, it now has tons of it. in the code and I was wondering, whether it is possible to have some similar behaviour as with the @DslMarker in place.
What I tried is a mixture of the following:
@DslMarker
annotation class DemoMarker
@DemoMarker
inline fun <T> T.build(@DemoMarker builder : T.() -> Unit) = this.apply(builder)
"mixture", because I ended up putting the annotation everywhere, but this doesn't have any effect. If I put it on a class it works as expected. Did I miss something and it is actually possible somehow? Or does anyone have an appropriate workaround for this, besides using also?
kotlin
kotlin
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
asked Nov 15 '18 at 17:03
RolandRoland
9,48211141
9,48211141
Can you inherit from that third-party classes? Probably inherit and mark your classes with@DslMaker?
– madhead
Nov 16 '18 at 11:59
That would be possible, but there are about ~4k classes in there... they are obviously generated from a schema. Maybe I can get the schema from somewhere and then just generate the sources from scratch and add the annotation while generating :-) still I think the question stays valid... and I hope there is some other workaround for this :-)
– Roland
Nov 16 '18 at 12:04
add a comment |
Can you inherit from that third-party classes? Probably inherit and mark your classes with@DslMaker?
– madhead
Nov 16 '18 at 11:59
That would be possible, but there are about ~4k classes in there... they are obviously generated from a schema. Maybe I can get the schema from somewhere and then just generate the sources from scratch and add the annotation while generating :-) still I think the question stays valid... and I hope there is some other workaround for this :-)
– Roland
Nov 16 '18 at 12:04
Can you inherit from that third-party classes? Probably inherit and mark your classes with
@DslMaker?– madhead
Nov 16 '18 at 11:59
Can you inherit from that third-party classes? Probably inherit and mark your classes with
@DslMaker?– madhead
Nov 16 '18 at 11:59
That would be possible, but there are about ~4k classes in there... they are obviously generated from a schema. Maybe I can get the schema from somewhere and then just generate the sources from scratch and add the annotation while generating :-) still I think the question stays valid... and I hope there is some other workaround for this :-)
– Roland
Nov 16 '18 at 12:04
That would be possible, but there are about ~4k classes in there... they are obviously generated from a schema. Maybe I can get the schema from somewhere and then just generate the sources from scratch and add the annotation while generating :-) still I think the question stays valid... and I hope there is some other workaround for this :-)
– Roland
Nov 16 '18 at 12:04
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53324535%2fkotlin-dsl-scope-control-on-external-non-changeable-classes-similar-to-dslmark%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53324535%2fkotlin-dsl-scope-control-on-external-non-changeable-classes-similar-to-dslmark%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you inherit from that third-party classes? Probably inherit and mark your classes with
@DslMaker?– madhead
Nov 16 '18 at 11:59
That would be possible, but there are about ~4k classes in there... they are obviously generated from a schema. Maybe I can get the schema from somewhere and then just generate the sources from scratch and add the annotation while generating :-) still I think the question stays valid... and I hope there is some other workaround for this :-)
– Roland
Nov 16 '18 at 12:04