Strip legacy history structure view #6241
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Are we going to replace this with something new in this release cycle? If not I would leave it in as long as we have a replacement. |
|
@bgruening this cannot be reached from the UI and there are no plans to fix it atm |
|
@bgruening Yep, @martenson Is correct on both points there. We're going to develop something similar in this coming release cycle, but will start from scratch using the current client stack. |
jmchilton
approved these changes
May 30, 2018
dannon
added
the
kind/refactoring
|
Is it this structure ?
That one is quite useful to me and was working in 18.05 ? Do we have an issue to track progress for this ? |
|
@mvdbeek No, it is not that structure view. That said, I'll have the future work I mentioned written up this week. |
|
OK, cool, sorry for the noise |
|
No worries at all. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes another (web, not API) controller endpoint and the associated mako. It has been non-navigable from the UI for quite some time now.
Per discussions, we're going to start from scratch here.