refactor: Use type imports for AJV where possible by lucas-koehler · Pull Request #2415 · eclipsesource/jsonforms
Navigation Menu
{{ message }}
eclipsesource / jsonforms Public
- Notifications You must be signed in to change notification settings
- Fork 421
Merged
refactor: Use type imports for AJV where possible#2415
lucas-koehler merged 1 commit intomasterfrom
refactor: Use type imports for AJV where possible#2415
lucas-koehler merged 1 commit intomasterfrom
Conversation
Copy link
Contributor
lucas-koehler
commented
Feb 3, 2025
lucas-koehler
commented
This makes it clearer where the actual AJV implementation is used and where we only depend on the typing.
This makes it clearer where the actual AJV implementation is used and where we only depend on the typing.
Copy link
✅ Deploy Preview for jsonforms-examples ready!
| Name | Link |
|---|---|
| 🔨 Latest commit | 903cef7 |
| 🔍 Latest deploy log | https://app.netlify.com/sites/jsonforms-examples/deploys/67a0bd7ad79c2200087ac81b |
| 😎 Deploy Preview | https://deploy-preview-2415--jsonforms-examples.netlify.app |
| 📱 Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
sdirix approved these changes Feb 4, 2025
lucas-koehler
deleted the
lk/use-ajv-type-imports
branch
lucas-koehler
added this to the
3.6 milestone
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants