René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Feast Web UI","articleBody":"**Is your feature request related to a problem? Please describe.**\nSeveral things are harder than they should be today:\n- Tag searching / filtering\n- Discovery of feature views / data sources / models\n- Understanding lineage of models are difficult.\n- Understanding what features are available / materialized to the online store\n- Managing features across projects\n\n**Describe the solution you'd like**\nA Feast Web UI that enables discovery of features, data sources, and models across projects. \n\n- [x] Tests checking that changes to the feast registry protos don't break the web UI (i.e. an integration test that starts up the Feast UI)\n- [x] a feast cli command like `feast ui` that scans subdirectories for `feature_store.yaml` and calls `feast registry-dump` and pipes it to a known location for the web UI to reference. It also should produce the `project-list.json `that we use for the landing page. This should also start the local web ui server.\n- [x] Improved search bar experience that does type-ahead suggestions on tag names\n- [x] release process that automatically publishes the npm package.\n\nAfter initial launch\n- [x] A project level description config (e.g. in `feature_store.yaml` which populates the landing page of a given project in the UI and is output in the \"registry\" dump)\n- [ ] Working across all types\n- [ ] Links to e.g. feast-dev documentation (e.g a ? that shows details on hover)\n- [ ] Flagging system for different UI components\n- [x] Custom plugin system\n- [x] Having a UI that dynamically updates + re-syncs against the registry file\n- [x] Migration towards perhaps https://github.com/protobufjs/protobuf.js/ instead of zod to parse data\n- [ ] There's a \"statistics\" page in feature views that needs data to be populated. It's hidden by default behind a flag, but once we start pulling sample data and statistics in generating the json dump, this can be re-enabled\n- [ ] Cleaned up UI for the data sets that gives information about the declared expectations\n- [ ] UI for the data sets that highlights validation errors in a saved dataset\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\nAdd any other context or screenshots about the feature request here.\n","author":{"url":"https://github.com/adchia","@type":"Person","name":"adchia"},"datePublished":"2022-03-02T03:27:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/2353/feast/issues/2353"}