Yonghwan SO
Yonghwan SO
From the definition of buffalo `Handler`: https://pkg.go.dev/github.com/gobuffalo/buffalo#Handler > It is the responsibility of the Handler to handle the request/response correctly. This statement also includes the responsibility of setting the HTTP...
The current design and implementation of `Worker` and `Simple` worker are somewhat ambiguous and they need to be redefined. The points of consideration could be: * Definition of Worker and...
`DefaultContext` implements `buffalo.Context` and this is the core context for buffalo's application flow, and it should be configured correctly to work properly with its functions. However, `DefaultContext` is currently public,...
The name `App` sounds like the only root of the application structure (could be a singleton) but actually, it is also a container of a group of URLs that is...
This PR addressed https://github.com/sirupsen/logrus/pull/1343#issuecomment-1188912003 (related to https://github.com/sirupsen/logrus/pull/1337) (Github's dependabot told that the recent update include CVE fix but I found the PR was reverted *reasonably*) 
The function `instrumentDriver()` registers a custom SQL driver with `sql.Register()` and it uses a decorated driver name as something like `instrumented-sql-driver-sqlite3` which is based on the driver name but actually...
Hello, how about make many-to-many more flexible by support some more customizing tags? https://github.com/gobuffalo/pop/blob/5fd1842ebd11190eaf64b8e31155aafabc62f069/associations/many_to_many_association.go#L76 I have some tables for example `stores` and table `consumers`, which is related each others as...
@paganotoni How about marking the repository as archived? It could help people to understand the project's status easily.
### Progress * [x] #41 * [ ] deprecating unwanted functions and clean up APIs ### Direction * just make it as an enhanced version of `os.Getenv()` families with virtual...
To address #2285