xevion/rdap
1
0
Fork 0
mirror of https://github.com/Xevion/rdap.git synced 2025-12-06 03:16:07 -06:00
Code Issues Packages Projects Releases Wiki Activity

ci: implement comprehensive CI/CD and workflow automation

Browse Source 
- Add GitHub Actions workflows for CI, release, and deployment
- Configure Renovate for automated dependency updates
- Set up Husky pre-commit hooks with lint-staged
- Add commitlint for enforcing Conventional Commits
- Configure semantic-release for automated versioning
- Add Prettier configuration for consistent formatting
- Reformat codebase with new formatting rules
This commit is contained in:
Xevion
2025-10-22 02:45:58 -05:00
parent 2c1f882cd9
commit c17f733da1
48 changed files with 5453 additions and 2422 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -35,11 +35,11 @@ But in all seriousness, my project does intend to have more features:
- Whois: RDAP is a newer protocol that is meant to replace Whois, but some servers still use Whois. I might add support for that.
- Punycode: Some domain names use punycode, which is a way to represent Unicode characters in ASCII. I might add support for working with these domains.
- Better Error Handling: The original RDAP client doesn't handle errors very well, or tell you what went wrong. I want to fix that.
- For example, when querying a TLD that does not have a RDAP server, or one that does not exist, the original client doesn't explain this very well.
- For example, when querying a TLD that does not have a RDAP server, or one that does not exist, the original client doesn't explain this very well.
- RDAP Schema Adherence: RDAP servers are supposed to follow a schema, but it appears a large number simply don't. I intend to provide handling for this.
- Essentially, two separate schemas will be available: one for basic type checking, and one for the RFC-compliant schema.
- If the server doesn't follow the RFC-compliant schema, the basic schema will be used instead.
- It's hard to tell at this moment if Typescript can handle this well, but I'll try.
- Essentially, two separate schemas will be available: one for basic type checking, and one for the RFC-compliant schema.
- If the server doesn't follow the RFC-compliant schema, the basic schema will be used instead.
- It's hard to tell at this moment if Typescript can handle this well, but I'll try.
[rdap]: https://rdap.xevion.dev
[nextjs]: https://nextjs.org