Timeline for Adjusting business logic conveniently through JSON and expression trees
Current License: CC BY-SA 4.0
18 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
S Dec 6, 2018 at 11:11 | history | bounty ended | t3chb0t | ||
S Dec 6, 2018 at 11:11 | history | notice removed | t3chb0t | ||
S Dec 5, 2018 at 10:13 | history | bounty started | t3chb0t | ||
S Dec 5, 2018 at 10:13 | history | notice added | t3chb0t | Reward existing answer | |
Dec 4, 2018 at 16:52 | vote | accept | t3chb0t | ||
Nov 29, 2018 at 21:03 | answer | added | Pieter Witvoet | timeline score: 3 | |
Nov 26, 2018 at 10:32 | comment | added | t3chb0t | @PieterWitvoet exactly. This is just the general framework. The business case needs to implement its own special expressions that actually do something useful with its own business objects etc. this is an experiment where I was designing a log-filter utilizing it (its API however is not longer up-to-date). | |
Nov 26, 2018 at 10:30 | comment | added | Pieter Witvoet |
Thanks. So the Color , SeatCount , HasColor and HasFeature expressions in the example would be business-specific extensions?
|
|
Nov 26, 2018 at 9:18 | comment | added | t3chb0t | @PieterWitvoet oh, sorry... posting everything would probably be too much but you can find the complete code here in my repository and exactly in this project and this are my tests that I have so far in the open-source part. | |
Nov 26, 2018 at 9:15 | comment | added | Pieter Witvoet |
I'm trying to get this to work, but it's missing several definitions that cannot easily be stubbed: Scope(this IExpression) , InvokeWithValidation(this IExpression) , Values<T>(this IEnumerable<IExpression>) , ValidateInItems(this IExpression, IExpressionContext) and ValidateOutItems(this IExpression, IExpressionContext) .
|
|
Nov 26, 2018 at 3:00 | history | tweeted | twitter.com/StackCodeReview/status/1066889439610322945 | ||
Nov 25, 2018 at 15:34 | comment | added | t3chb0t | @PieterWitvoet oh yeah, I'm pretty sure and it's already paying off ;-) being able to introduce changes that do not require the entire development and deployment process is a great time saver. This should be seen as a slightly more complex configuration rather than a scripting language. | |
Nov 25, 2018 at 15:16 | comment | added | Pieter Witvoet | It looks like you've written a tiny scripting language with a JSON-based syntax. The example looks rather verbose - in C# that would only take a handful of lines. Are you sure this will make it easier to adjust and maintain your program? | |
Nov 24, 2018 at 13:55 | history | edited | Heslacher | CC BY-SA 4.0 |
edited body
|
Nov 24, 2018 at 12:00 | history | edited | t3chb0t | CC BY-SA 4.0 |
added 7 characters in body
|
Nov 24, 2018 at 11:53 | history | edited | t3chb0t | CC BY-SA 4.0 |
edited body
|
Nov 24, 2018 at 11:37 | history | asked | t3chb0t | CC BY-SA 4.0 |