Custom plugin for @hey-api/openapi-ts that generates Hono createRoute(...) definitions from an OpenAPI spec using Zod output.
Pipeline:
OpenAPI → IR → RouteInfo → RouteDefinition → Hono DSL → hono-plugin.gen.ts
| // [Verse 1] | |
| // "Package I-T dot Nanowar dot Of Steel dot hello world (Semicolon)" | |
| // "Public class Hello World Main Launcher Class (Open brackets)" | |
| package it.nanowar.ofsteel.helloworld; | |
| public class HelloWorldMainLauncherClass { | |
| // "Public hello world main launcher class round brackets int foo (Close brackets)" | |
| // Super round brackets this dot foo equals foo (Semicolon, close brackets) |
| import { vi } from 'vitest'; | |
| import type { Mock } from '@vitest/spy'; | |
| // type-definitions | |
| export type FetchMock = Mock<typeof global.fetch> & AdditionalMethods; | |
| interface AdditionalMethods { | |
| mockResponse(fn: ResponseProvider): FetchMock; // @prettier-ignore | |
| mockResponse(response: string, responseInit?: ResponseInit): FetchMock; |
| import type { Connect, Plugin, UserConfig, ViteDevServer } from "vite"; | |
| import type { IncomingMessage, ServerResponse } from 'http'; | |
| import type { Application } from 'express'; | |
| export interface VitePluginExpressConfig { | |
| appName?: string | |
| initAppOnBoot?: boolean | |
| exportName?: string | |
| appPath: string; | |
| } |
My career as a web developer started back in 2009. At the time of writing, that is already 15 years ago! Web development used to be so much different. Some things were simpler, other things where more difficult. In this article, I'd like to look back on all the challenges we faced, how we've dealt with them. We will discuss what has become legacy, and what to expect in the near future.
// My first experience with writing web pages was in 2003, when I was a 12 year old teenager, trying to make a simple website with HTML and CSS. For me, this was
A lot was going on by the end of the 2000s. The Web 2.0 trend had lead to more dynamic web pages. JavaScript became more and more important. We started to utilize AJAX more and more, which allows you to make your webpage more interactive with the server. It was no surprise that in 2010, we saw single-page application (SPA) frameworks like Backbone.JS and Angular.JS being i
My career as a web developer started back in 2009. At the time of writing, that is already 15 years ago! Web development used to be so much different. Some things were simpler, other things where more difficult. In this article, I'd like to look back on all the challenges we faced, how we've dealt with them. We will discuss what has become legacy, and what to expect in the near future.
// My first experience with writing web pages was in 2003, when I was a 12 year old teenager, trying to make a simple website with HTML and CSS. For me, this was
A lot was going on by the end of the 2000s. The Web 2.0 trend had lead to more dynamic web pages. JavaScript became more and more important. We started to utilize AJAX more and more, which allows you to make your webpage more interactive with the server. It was no surprise that in 2010, we saw single-page application (SPA) frameworks like Backbone.JS and Angular.JS being i
My career as a web developer started back in 2009. At the time of writing, that is already 15 years ago! I remember that web development used to be so much different. Some things were simpler, other things where more difficult. In this article, I'd like to look back on all the challenges we faced, how we've dealt with them. We will discuss the things that have become legacy, and what to expect in the near future.
// My first experience with writing web pages was in 2003, when I was a 12 year old teenager, trying to make a simple website with HTML and CSS. For me, this was
A lot was going on by the end of the 2000s. The Web 2.0 trend had lead to more dynamic web pages. JavaScript became more and more important. We started to utilize AJAX, which allows you to become more interactive with the server. It was no surprise that in 2010, single-page application (SPA) frameworks like Backbone.JS and Angular.JS where intro
| package com.foo.util.specification.jdbc | |
| import org.springframework.context.ApplicationEventPublisher | |
| import org.springframework.data.jdbc.core.JdbcAggregateTemplate | |
| import org.springframework.data.jdbc.core.convert.DataAccessStrategy | |
| import org.springframework.data.jdbc.core.convert.JdbcConverter | |
| import org.springframework.data.jdbc.repository.support.JdbcRepositoryFactory | |
| import org.springframework.data.mapping.callback.EntityCallbacks | |
| import org.springframework.data.relational.core.dialect.Dialect | |
| import org.springframework.data.relational.core.dialect.RenderContextFactory |
| import { HttpErrorResponse, HttpRequest, HttpResponse } from '@angular/common/http'; | |
| import { Router } from '@angular/router'; | |
| import { createService, createSpyObject } from '@netbasal/spectator'; | |
| import { of, throwError } from 'rxjs'; | |
| import { RedirectInterceptor } from './redirect-interceptor.service'; | |
| import anything = jasmine.anything; | |
| describe('RedirectInterceptorService', () => { | |
| const spectator = createService({ | |
| service: RedirectInterceptor, |