* feat(client): add `tabs` support
* chore: apply fixes
* test: fix types
* build: pw again
* build: more attempts to improve PW
* fix: regressions after refactoring to tabs
* style: apply TS style fixes
* build: more PW
* test: run a problematic test in serial mode
* test: no parallel pw
* test: fix race condition in PW
* test: pw one worker no retry
* fix: work around l12 breaking change
* build: fix testing job to switch properly
* build: provide proper versions that support laravel version switching
these only to allow switching without problems. The main tooling chain will be using the latest versions.
* build: run E2E tests with the current branch
* style: apply php style fixes
* build: cache PW browsers in GHA
* build: fix step name
* build: require branch name as argument for e2e setup
* chore: improve the e2e setup file traceability
* chore: improve file comment
* build: pass branch name as argument for e2e setup
* build: attempt to fix PW browser cache in GHA
* build: fix syntax issue with the e2e GHA
* build: also cache php installation for e2e test
* build: attempt to fix PW browsers cache
* build: don't attempt to cache php installation in e2e
it cannot be cached because it is installed in temporary runner directory
* chore: setup E2E foundation
* chore: use http to clone the repo
this will make it work in GHA (no SSH is needed).
* chore: add missing dependencies to e2e ci
This commit represents the complete foundational codebase for Nimbus Alpha, a Laravel package that provides an integrated, in-browser API client with automatic schema discovery from validation rules.
IMPORTANT: This is a squashed commit representing the culmination of extensive development, refactoring, and architectural iterations. All previous commit history has been intentionally removed to provide a clean foundation for the public alpha release.
The development of Nimbus involved:
- Multiple architectural refactorings
- Significant structural changes
- Experimental approaches that were later abandoned
- Learning iterations on the core concept
- Migration between different design patterns
This messy history would:
- Make git blame confusing and unhelpful
- Obscure the actual intent behind current implementation
- Create noise when reviewing changes
- Reference deleted or refactored code
If git blame brought you to this commit, it means you're looking at code that was part of the initial alpha release. Here's what to do:
1. Check Current Documentation
- See `/wiki/contribution-guide/README.md` for architecture details
- Review the specific module's README if available
- Look for inline comments explaining the reasoning
2. Look for Related Code
- Check other files in the same module
- Look for tests that demonstrate intended behavior
- Review interfaces and contracts
3. Context Matters
- This code may have been updated since alpha
- Check git log for subsequent changes to this file
- Look for related issues or PRs on GitHub
---
This commit marks the beginning of Nimbus's public journey. All future
commits will build upon this foundation with clear, traceable history.
Thank you for using or contributing to Nimbus!
