Closed mmaelicke closed 2 years ago
I just created the legacy-topic-select
branch and pushed it to Github.
I will move on to removing topic-related code from the main branch, but wouldn't it be easier to remove the code directly from the weather-climate-merge
branch where you (@mmaelicke ) already don't use a lot of the topic related code anymore?
I just created the
legacy-topic-select
branch and pushed it to Github. I will move on to removing topic-related code from the main branch, but wouldn't it be easier to remove the code directly from theweather-climate-merge
branch where you (@mmaelicke ) already don't use a lot of the topic related code anymore?
sure, I'll remove the topic select file in that banch and add the changes to #77
Okay, so I will start removing topic related code from the weather-climate-merge
branch.
I think I found all occurrences of topic related code (https://github.com/hydrocode-de/RUINSapp/pull/77/commits/d2ecb2f9dc0a2d84bbc99b9357eb8c4ceadf3f2a). There was'n really much left.
Topical story lines Since a plethora of topics related to changes in climate, weather and possible adaptation exists, we suggest several topics reoccurring in each chapter. These topics can be used as story lines guiding through the app.
With the new application layout, there is no need for the concept of topics anymore.
We need to:
To keep the app cleaner, I would do that soon. At the same time, I don't want to lose the topic-select code. My approach: copy the topic-select into a newly created
compontents.legacy
submodule. Then push this to a new branch calledlegacy-topic-select
and after that remove everything from main branch. If we then never ever need the topic selec again, we can simply remove that branch.@AlexDo1 or @lucfr you can go for this issue by assigning yourself