Hey, I would like to get some feedback on the library I'm developing for fiber v3. It basically automatically generates swagger.yaml + swagger.json + swagger editor ui from your fiber routes.
It can automatically generate the route + the route path parameters. If you wanna provide more info, I've created a simple interface that wraps the fiber's router and isn't too annoying ... or you can use `gofiberswagger.RegisterRoute()` to add the definition on your own (without touching the existing code).
The library uses reexported github.com/getkin/kin-openapi types, that means that you can specify ANY openapi field you wanna (not only in routes, but also in the general config, eg. auth / security schemes / title / openapi version / etc).
I've implemented it into some of my personal projects and tbh I love it, that's why I decided to share it with y'all. I know about swaggo/swag, however I don't like how my code looks while using it.
I've created some basic examples inside the `/examples/` folder, so be sure to check them out! Any feedback would be appreciated.
First thing that comes to mind is the need to link against libraries across platforms. Imagine that my app depends on opencv, if I wanted to statically link everything on my Windows machine, I need to compile opencv for Linux on my windows machine (or use pre-compiled binaries). Also, if you link against libraries dynamicaly, it's likely you can compile them on the host machine (or in a container) with more optimizations enabled. And the last thing is probably the ability to "freeze" the whole "system" environment (like folders, permissions, versions of system libraries).
Personally, I use containers to quickly spin-up different database servers for development or as an easy way of deployment to a cloud service...
In theory, you must have written some code to train the models + download the data ... just openning this code + adding logging to store the sources trained on, you could achieve trully "open source" (anybody can now go and scrape + train the same way you did and achieve the same outcome/model)
I'm not saying "opening models is bad", it's good. However imo it would be nice to have a semantic way to differentiate between those two
as a high school student, I'm more hesitant to go into CS degree not because of chatgpt but because it is constantly marketed as a high income job and A LOT of people are choosing/learning it. I wonder if it's gonna be the same in 10 years or so. Chatgpt/copilot make stuff easier and there are only so much CRUD apps to be made :/
hi ^^, limited knowledge as well, however I'm pretty sure the issue is that Harvest allows all urls to be used as callback urls. You should tell microsoft to allow only certain urls as callbacks. eg, when setting up the workflow, they probably used a wildcard as an allow list of callback urls, instead of creating an actual list of trusted callback urls. I think that's what's happening here, could be totally wrong tho :D
Personally, I really like svelte. Either use a bundler + js library for redirects OR SvelteKit with static adapter (https://kit.svelte.dev/docs/adapter-static). Fyi I use the latter since it's easier to setup and bit more trouble-free to use overall :D
Yeah, afaik, in the old template version `npm run export` activated the `expo export` and THAT got deprecated (recently), however at the time (about half a year ago) I thought that the `--local` flag was getting deprecated. Sorry, that was a huge misunderstanding on my end!
yes, you are right, however, AFAIK you still need to be logged + have it linked to eas project (because it uses eas credentials) + this method is planned to be deprecated soon [?] (I'm 100% sure I read stuff like this when researching it like half a year ago, but cannot find it for the love-of-god atm :D, but I would like to be proved otherwise, because the build step is the only thing I disliked about expo long-term wise)
... now looking more into it, I probably mistook `npm run export` / `expo build` with `eas build --local`. Is this correct?
Tbh, I liked expo, but since you cannot build locally nowdays (you can eject and build, but that won't work 99% of the time, literally didn't work for me on the hello world example), I kinda just threw it in the "cool, but won't use" bucket for time beeing :/, could change in the future, but I don't know how I feel about 3d party service (EAS) building my app and holding my signing certificates (yet)
chip on it, e-ink display sawthered on and etc, just get me from my prototype to a full on product. Basically, I want to advance my skills to the next level, but I struggle to find how :/ .... you seem to have experience in this kind of stuff, could you please answear some of these questions?
Ps: accidentally posted before I finished the comment and using mobile client without ability to edit comments :d
Ps2: these comments are kinda out of context, but it's something that's bothering me for more than a month now.
Hi, just asking, I'm interested in embedded but as an outsider I fail to understand how would I go about making custom board? I googled a lot, but I still fail to grasp how do you make the board? How do you program the chip? How can you test your board? How can you prototype on an arduino, if you'll use different architecture STM vs Atmega, etc...
I've done some arduino projects using VSCode and Platformio and I want to level up my skill level, however I've been struggling to find a resources that goes throught the process of actually making the product from scratch (starts with nothing and ends with a programmed product on custom board). For example, I have this project of mine where I make smart watches using an arduino and e-ink paper display. I would like to read / watch a resource where I learn to design a board that has custom STM32
It can automatically generate the route + the route path parameters. If you wanna provide more info, I've created a simple interface that wraps the fiber's router and isn't too annoying ... or you can use `gofiberswagger.RegisterRoute()` to add the definition on your own (without touching the existing code).
The library uses reexported github.com/getkin/kin-openapi types, that means that you can specify ANY openapi field you wanna (not only in routes, but also in the general config, eg. auth / security schemes / title / openapi version / etc).
I've implemented it into some of my personal projects and tbh I love it, that's why I decided to share it with y'all. I know about swaggo/swag, however I don't like how my code looks while using it.
I've created some basic examples inside the `/examples/` folder, so be sure to check them out! Any feedback would be appreciated.