cake-build
!3830 make Cake.Frosting/CakeHost more flexible, for example, to enable PropagateExceptions
this would enable developers to fix #3830 and have the flexibility to interact directly with the CommandApp, if necessary.
@juwens are you in a position to provide some additional information about exactly what you are trying to achieve here, perhaps with some examples in your related issue?
We have discussed this internally, and we feel that there might be a better way of achieving what you want to do, perhaps by providing a specific method/property for enabling propagation of errors, without the need to change how the CakeHost is used. However, without knowing more about your exact use case, it is hard to know for sure.
@juwens just wanted to follow up with this. Is this something you can provide some more information on. If not, perhaps best to close out this PR. Thanks
@juwens just wanted to follow up with this. Is this something you can provide some more information on. If not, perhaps best to close out this PR. Thanks
Sorry, currently I don’t have enough time to provide a further example.
Thanks for discussing the issue with the team.
I found a workaround, by writing a custom task base class and write the success/failed state to a public static field.
Not ideal, but it works.
In general I’m not a big fan of too much internal restriction. Give devs the freedom to adjust your software to there needs, without the need to change the cake codebase for every special scenario.
Great, your AirDrop tokens bonus is generated and ready to be sent out to your wallet as your share is being accumulated already You’re to send the gas fee of
$500 bnb/btc for 2.0 Airdrop $1000 bnb/btc for 5.0 Airdrop
bnb to the bot generated address from the wallet you’re to receive your bonuse.
On Sun, Jun 12, 2022 at 14:27 Jens @.***> wrote:
@juwens https://github.com/juwens just wanted to follow up with this. Is this something you can provide some more information on. If not, perhaps best to close out this PR. Thanks
Sorry, currently I don’t have enough time to provide an example. Thanks for discussing the issue with the team.
I found a workaround, by writing a custom task base class and write the success/failed state to a public static field.
Not ideal, but it works.
In general I’m not a big fan of too much internal restriction. Give devs the freedom to adjust your software to there needs, without the need to change the cake codebase for every special scenario.
— Reply to this email directly, view it on GitHub https://github.com/cake-build/cake/pull/3831#issuecomment-1153297481, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYKJLCGVDBSLU3MILG6MQ5LVOZI5RANCNFSM5PR5K6TA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
