* slack_search.py * rem * fix: get elements * feat: better stack message processing * fix: mypy * fix: url parsing * refactor: federated search * feat: proper chunking + source filters * highlighting + source check * feat: forced section insertion * feat: multi slack api queries * slack query expansion * feat: max slack queries env * limit slack search to avoid overloading the search * Initial draft * more * simpify * Improve modal * Fix oauth flow * Fully working versino * More nicities * Improved cascade delete * document set for fed connector UI * Fix source filters + improve document set selection * Improve callback modal * fix: logging error + showing connectors in admin page user settings * better log * Fix mypy * small rei comment * Fix pydantic * Improvements to modals * feat: distributed pruning * random fix * greptile * Encrypt token * respect source filters + revert llm pruning ordering * greptile nit * feat: thread as context in slack search * feat: slack doc ordering * small improvements * rebase * Small improvements * Fix web build * try fix build * Move to seaprate model file * Use default_factory * remove unused model --------- Co-authored-by: Rei Meguro <36625832+Orbital-Web@users.noreply.github.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
Install node / npm: https://docs.npmjs.com/downloading-and-installing-node-js-and-npm
Install all dependencies: npm i
Then, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
Open http://localhost:3000 with your browser to see the result.
Note: if you are having problems accessing the ^, try setting the WEB_DOMAIN env variable to
http://127.0.0.1:3000 and accessing it there.
Testing
This testing process will reset your application into a clean state. Don't run these tests if you don't want to do this!
Bring up the entire application.
- Reset the instance
export PYTEST_IGNORE_SKIP=true
pytest -s tests/integration/tests/playwright/test_playwright.py
- Run playwright
cd web
npx playwright test
To run a single test:
npx playwright test landing-page.spec.ts
If running locally, interactive options can help you see exactly what is happening in the test.
npx playwright test --ui
npx playwright test --headed
- Inspect results
By default, playwright.config.ts is configured to output the results to:
web/test-results
- Upload results to Chromatic (Optional)
This step would normally not be run by third party developers, but first party devs may use this for local troubleshooting and testing.
cd web
npx chromatic --playwright --project-token={your token here}