Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wildcard handler #28

Open
elee1766 opened this issue Jul 12, 2024 · 2 comments
Open

wildcard handler #28

elee1766 opened this issue Jul 12, 2024 · 2 comments

Comments

@elee1766
Copy link

is it possible to register wildcard handler?

i would like to support arbitrary names, but it seems i cannot hook into the parser with a wildcard handler.

is there a way to iterate across the chunks manually easily?

@mazrean
Copy link
Owner

mazrean commented Jul 14, 2024

@elee1766
Hello! Thank you for your question regarding the potential for wildcard handlers in FormStream.

At present, there are no plans to support wildcard handlers in FormStream. This decision stems from the fact that the functionality of wildcard handlers can be effectively replicated by using NextPart from mime/multipart.

Regarding your experience with applications such as tuxpaint/gopaste, which I understand might be related to your work, I noticed there could be challenges in handling Bad Requests. If this is the case, I am exploring the possibility of introducing an option to generate an error when unexpected fields are encountered. This addition aims to provide a more robust and clear handling mechanism, enhancing the library’s utility in scenarios similar to yours.

Please let me know if this addresses your concerns or if there are other features you would like to see implemented in FormStream.

@elee1766
Copy link
Author

elee1766 commented Jul 14, 2024

I wanted to also handle arbitrary parameters.

maybe I should just use the underlying multipart reader then.

I mostly wanted to not do the work with all the buffering, but the go built in parser doesn't respect order, so I used your package.

would you consider a "fallback" handler which is used for unrecognized chunks?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants