- merged many PRs.
|Widget Connector||urlhttps://docs.google.com/document/d/1GnQKMyM4FMaEKm9UqIw3QQzI_DiiyqpXtf0k5cPoAaw/edit?usp=sharingClowder 2.0|
- next week, plan to demo the workbench integration extractor. explained how it is set up
- has been reviewing grid view PR, seems to be stringifying JSON in a way that causes high counts, left comments. we can do release now and fix this after merge.
Luigi: look at the tile being used and make sure there aren't additional changes we need to make (see app/views/files/tile.scala.html)
- updating PR for the space bytes count, then ready for review
- Fixed auto-deploy problem in industry cluster (yay base64 encoding!)
- Created pro/cons list for frontend of Clowder for 2.0.
- PROS - simultaneous development of back and frontend, not as tightly coupled. Easier to implement new design from scratch vs. modifying current view.
- REQUIREMENTS - need auth piece, may need JWT or similar token for this for separate frontend.
- Previewers - rewriting was cleanest vs. wrapping or porting. Some are easier to duplicate than others.
- For missing api endpoints or missing parameters or missing content response, need a smooth workflow for doing that. Overall like separate frontend.