Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read custom visualizations. #8077

Closed
Tracked by #7685
farmaazon opened this issue Oct 16, 2023 · 5 comments · Fixed by #8180
Closed
Tracked by #7685

Read custom visualizations. #8077

farmaazon opened this issue Oct 16, 2023 · 5 comments · Fixed by #8180
Assignees
Labels
-gui d-easy Difficulty: little prior knowledge required p-medium Should be completed in the next few sprints

Comments

@farmaazon
Copy link
Contributor

farmaazon commented Oct 16, 2023

We should read visualization from project's visualization directory (using existing lsRPC methods) + looking for updates of those files, then compile them (same way as built-in visualizations are now compiled) and register them in the registry.

Managing dependencies is not in the scope of this task.

@farmaazon farmaazon mentioned this issue Oct 16, 2023
@farmaazon farmaazon added d-easy Difficulty: little prior knowledge required p-medium Should be completed in the next few sprints -gui labels Oct 16, 2023
@enso-bot
Copy link

enso-bot bot commented Oct 30, 2023

E-Hern Lee reports a new STANDUP for yesterday (2023-10-30):

Progress: - implementation

  • (wip) address review

other issues -

  • fix regression causing node colors to not be determined by groups It should be finished by 2023-11-03.

Next Day: finish addressing review, final features (removing old <style> tags, reloading visualization o refresh)

@enso-bot
Copy link

enso-bot bot commented Oct 31, 2023

E-Hern Lee reports a new STANDUP for yesterday (2023-10-31):

Progress: - finish addressing review; address new reviews

  • remove old style tags
  • reload visualizations on refresh
  • some (not all) tests It should be finished by 2023-11-03.

@enso-bot
Copy link

enso-bot bot commented Nov 1, 2023

E-Hern Lee reports a new STANDUP for yesterday (2023-11-01):

Progress: - address reviews again

  • begin work on mocks required for histoire story to work

other issues -

  • initial code for payment page (add Stripe dependency, new page in router, some basic styling. todo: make the picker into a radio button)
  • simplifying + changing CSS for auth flow pages. the design is not ready yet, but this PR should make a lot of progress towards that even before the design is ready
  • merged PR to fix flaky lint caused by edge cases that are inconsistently triggered by prop testing It should be finished by 2023-11-03.

@enso-bot
Copy link

enso-bot bot commented Nov 3, 2023

E-Hern Lee reports a new STANDUP for yesterday (2023-11-02):

Progress: - finish implementing mocks

other issues -

  • copy footer and eu-projects pages for new website
  • basic (rough) implementation of nav panel for carousel for new website It should be finished by 2023-11-03.

@enso-bot
Copy link

enso-bot bot commented Nov 3, 2023

E-Hern Lee reports a new STANDUP for today (2023-11-03):

Progress: - test "user-defined viz" story and fix bugs

  • attempt to clean up code related to mocks

other issues -

  • debug and get rid of undesired horizontal scrolling for new website
  • various minor bugfixes for new website
  • general tidying up of codebase for new website? (mostly style -> tailwind classNames)
  • minor qol for new website (minor ssg improvements, redirect 404 page to home page) It should be finished by 2023-11-03.

@mergify mergify bot closed this as completed in #8180 Nov 3, 2023
mergify bot pushed a commit that referenced this issue Nov 3, 2023
- Closes #8077

# Important Notes
Tests are still WIP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-gui d-easy Difficulty: little prior knowledge required p-medium Should be completed in the next few sprints
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants