Cortex bekommt eine eigene Seite und einen Menuepunkt - #4
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Der Cortex — die Wissens-Ansicht als zoombares Netz — ist seit gestern
live, aber man kam nur ueber Umwege hin: erst
/pulsoeffnen, dann imRegister oben klicken. Ein direkter Aufruf landete auf der 404-Seite.
Zwei Dateien:
pages/cortex/index.tsx— neue Seite, gebaut wiepages/puls/index.tsx,iframe auf
/api/mothership/karte(der Pfad steht laengst in derPositivliste des Proxys, dort ist nichts zu aendern).
components/SideNavigation.tsx— Menuepunkt „Cortex" hinter Puls,Tastenkuerzel
GdannC(war frei; belegt waren nur G B/T/M/P/S).Abnahme: Typecheck gruen, eslint auf der neuen Datei gruen, Unterschied
genau diese zwei Dateien.