Advent of Code is now back for a limited time only! Complete as many challenges as you can to earn those badges you may have missed in December. Learn more about how to participate here!
Weekly Challenges
Solve the challenge, share your solution and summit the ranks of our Community!Also available in | Français | Português | Español | 日本語
IDEAS WANTED
Want to get involved? We're always looking for ideas and content for Weekly Challenges.
SUBMIT YOUR IDEA
Spoiler
I refrain from manually typing lists in drop down boxes when I can, so I have a little App_1 prep that created the drop down list. I left it in my workflow but disabled it in a container since it's not needed after dev technically.
A nice, simple chained app. The very essence of Asparagus.
Not explaining that.
Spoiler
The first dropdown in App 1 is populated from the incoming data. The second and third are output from the prior app and imported as an external source in the Dropdown tool.
From there, it's simple filtering, outputting two files from the first two apps (not required in the final app) which are the data file and the file to populate the dropdown tool with the available selections.
Then simply set up your interface designer to allow the chaining and Robert's your father's brother.
From there, it's simple filtering, outputting two files from the first two apps (not required in the final app) which are the data file and the file to populate the dropdown tool with the available selections.
Then simply set up your interface designer to allow the chaining and Robert's your father's brother.
Noice.
