Veganism Social

Emelia 👸🏻Over the past few days in the small moments when I've been able to work I've been experimenting with porting Hasher-Matcher-Actioner from Flask to FastAPI, and I now have it mostly working with an existing database.It's been interesting working with python because I don't work with it much, but FastAPI still feels very much like Express in terms of how things are written — lots of building your own framework essentially, instead of "here's the given path", which can be daunting.I still need to work out Alembic and migrations, but I have it working against an existing database with the same schema. Also need to figure out building CLI tools that accompany the server, where flask has that built-in<a href="https://hachyderm.io/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://hachyderm.io/tags/FastAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FastAPI</a>

Ranjan KumarBuilt my first AI chatbot using LangGraph + FastAPI + React! 🚀 It’s live, it works great on mobile & desktop, and yes — it's open source too.From clean chat bubbles to smart error handling, I’ve shared everything in detail.👉 Read full here: <a href="https://iranjankumar.com/building-my-first-very-basic-ai-chatbot-with-langgraph-added-react-frontend-and-fastapi-backend/" rel="nofollow noopener" translate="no" target="_blank">https://iranjankumar.com/building-my-first-very-basic-ai-chatbot-with-langgraph-added-react-frontend-and-fastapi-backend/</a><a href="https://mastodon.social/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://mastodon.social/tags/chatbot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chatbot</a> <a href="https://mastodon.social/tags/langgraph" class="mention hashtag" rel="nofollow noopener" target="_blank">#langgraph</a> <a href="https://mastodon.social/tags/reactjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#reactjs</a> <a href="https://mastodon.social/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://mastodon.social/tags/groq" class="mention hashtag" rel="nofollow noopener" target="_blank">#groq</a> <a href="https://mastodon.social/tags/fullstackdeveloper" class="mention hashtag" rel="nofollow noopener" target="_blank">#fullstackdeveloper</a> <a href="https://mastodon.social/tags/indiedev" class="mention hashtag" rel="nofollow noopener" target="_blank">#indiedev</a> <a href="https://mastodon.social/tags/buildinpublic" class="mention hashtag" rel="nofollow noopener" target="_blank">#buildinpublic</a>

Marcus AlmeidaBuilt a Python library to enable HTTP method override through form parameters or headers — supports PUT, DELETE, PATCH, and more.<a href="https://github.com/marcuxyz/wsgi_method_override" rel="nofollow noopener" translate="no" target="_blank">https://github.com/marcuxyz/wsgi_method_override</a><a href="https://mastodon.social/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://mastodon.social/tags/wsgi" class="mention hashtag" rel="nofollow noopener" target="_blank">#wsgi</a> <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#http</a> <a href="https://mastodon.social/tags/flask" class="mention hashtag" rel="nofollow noopener" target="_blank">#flask</a> <a href="https://mastodon.social/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://mastodon.social/tags/django" class="mention hashtag" rel="nofollow noopener" target="_blank">#django</a>

spla :fed: :vim:700 "commits" ja 😅 <a href="https://mastodont.cat/tags/appy" class="mention hashtag" rel="nofollow noopener" target="_blank">#appy</a> <a href="https://mastodont.cat/tags/fastAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastAPI</a> <a href="https://mastodont.cat/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>

TheaFinally got my FastAPI app deployed on Vercel after some trial and error 💪 Wrote down everything I learned because I know I'll forget these steps in 2 weeks😅 Maybe it'll help someone else too 👩‍💻 <a href="https://mastodon.social/tags/FastAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FastAPI</a> <a href="https://mastodon.social/tags/Vercel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vercel</a> <a href="https://mastodon.social/tags/DEVCommunity" class="mention hashtag" rel="nofollow noopener" target="_blank">#DEVCommunity</a> <a href="https://dev.to/highflyer910/deploy-your-fastapi-app-on-vercel-the-complete-guide-27c0" rel="nofollow noopener" translate="no" target="_blank">https://dev.to/highflyer910/deploy-your-fastapi-app-on-vercel-the-complete-guide-27c0</a>

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕Choosing a hash function for 2030 and beyond: SHA-2 vs SHA-3 vs BLAKE3As everyone knows, "temporary fixes" are nothing but temporary. Unfortunately, the same is true for cryptography: unless security is your core value-proposition, crypto algorithms are almost never updated, and that's how we end up with SHA1-hashed password in 2024 🤦‍♂️# <a href="https://kerkour.com/fast-secure-hash-function-sha256-sha512-sha3-blake3" rel="nofollow noopener" translate="no" target="_blank">https://kerkour.com/fast-secure-hash-function-sha256-sha512-sha3-blake3</a><a href="https://chaos.social/tags/hash" class="mention hashtag" rel="nofollow noopener" target="_blank">#hash</a> <a href="https://chaos.social/tags/hashfunctions" class="mention hashtag" rel="nofollow noopener" target="_blank">#hashfunctions</a> <a href="https://chaos.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://chaos.social/tags/sha2" class="mention hashtag" rel="nofollow noopener" target="_blank">#sha2</a> <a href="https://chaos.social/tags/hashing" class="mention hashtag" rel="nofollow noopener" target="_blank">#hashing</a> <a href="https://chaos.social/tags/itsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#itsec</a> <a href="https://chaos.social/tags/itsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#itsecurity</a> <a href="https://chaos.social/tags/sha3" class="mention hashtag" rel="nofollow noopener" target="_blank">#sha3</a> <a href="https://chaos.social/tags/BLAKE3" class="mention hashtag" rel="nofollow noopener" target="_blank">#BLAKE3</a> <a href="https://chaos.social/tags/fast" class="mention hashtag" rel="nofollow noopener" target="_blank">#fast</a> <a href="https://chaos.social/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://chaos.social/tags/feature" class="mention hashtag" rel="nofollow noopener" target="_blank">#feature</a>

nathanI wrote a few words on my new work environment — I’m not an iOS dev amymore, but write <a href="https://chaos.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> code with <a href="https://chaos.social/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> nowadays. And I also decided to postpone the purchase of a new computer for another month or so. It will most likely be a <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a><a href="https://zeitschlag.net/new-job-new-os/" rel="nofollow noopener" translate="no" target="_blank">https://zeitschlag.net/new-job-new-os/</a>

dilawarI am probably holding them wrong!This time I tried writing a web app not in <a href="https://fosstodon.org/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#php</a> but <a href="https://fosstodon.org/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> + <a href="https://fosstodon.org/tags/sqlmodel" class="mention hashtag" rel="nofollow noopener" target="_blank">#sqlmodel</a> (python) and <a href="https://fosstodon.org/tags/vue3" class="mention hashtag" rel="nofollow noopener" target="_blank">#vue3</a> ( javascript). It kind of works well but refactoring is a nightmare. In the beginning, it felt like I was having the best of both worlds -- Python and Vue3. Dev speed was good. Now maintaining and refactoring make me feel like I am having the worst of both worlds.As a single dev, I should have stayed with <a href="https://fosstodon.org/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#php</a>!

Chris Gioran 💔So, as it turns out, I have a new project in the works.And it's not a new DBMS. It's a data/publishing platform for journalists. Not quite a CMS, not quite an archival service. We're gathering requirements now, so I'll have a better description soon.I am looking at <a href="https://fosstodon.org/tags/FastAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FastAPI</a> for the backend w/#Astro for the frontend/client. I've never built anything like this before, so expect silliness forthwith.

Adam ♿Take me back to ASP.NET please.<a href="https://github.com/fastapi/fastapi/discussions/13449" rel="nofollow noopener" translate="no" target="_blank">https://github.com/fastapi/fastapi/discussions/13449</a><a href="https://aus.social/tags/FastAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FastAPI</a> <a href="https://aus.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>

Aaron LongchampsThe goal for Rack Root is to inventory my home lab and learn some web dev (FE+BE) along the way. I'm now at the point where I think I'll have the biggest challenge: IPAM / networking data.I'm anticipating that this part will be the most complex because of all the relationships. This is also going to test my API and database design skills, to say nothing of the front end design.At the start, I'm going to need a good IPv4 address handler library, ways to CRUD network segments, CRUD DHCP ranges, assign static IPs to devices, and similar.I also will have the data to generate visualizations of IP address usage, and plan to do that at some point.I fully expect to take advantage of things like Vuetify 3's v-card element which should help with some nifty graphical layouts.<a href="https://infosec.exchange/tags/rackroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#rackroot</a> <a href="https://infosec.exchange/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://infosec.exchange/tags/applicationdesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#applicationdesign</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#backend</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://infosec.exchange/tags/vuetify" class="mention hashtag" rel="nofollow noopener" target="_blank">#vuetify</a>

Aaron LongchampsFinished the NewItem.vue page for now with a better layout, date pickers for purchase date and warranty expiration, and a placeholder for devices on the network.My next plan is to start designing the networking piece of Rack Root and figure out which pieces I'll need to put in place. This will include the network zone, DHCP ranges, and subnet mask info. Devices on the network can be DHCP or static which is data I plan to track.Items will have the ability to use 0..n network interfaces which accounts for things not on the network such as hard drives, single-NIC devices such as laptops, and multi-NIC devices such as network devices. All of that can go into the database.By the time it's done, I should have the data to generate a pretty good picture of the network layout such as DHCP range utilization and IP utilization. Somewhere along the way I'll need to figure out subnet math, too. Yay.<a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://infosec.exchange/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://infosec.exchange/tags/vuetify" class="mention hashtag" rel="nofollow noopener" target="_blank">#vuetify</a> <a href="https://infosec.exchange/tags/rackroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#rackroot</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://infosec.exchange/tags/sideproject" class="mention hashtag" rel="nofollow noopener" target="_blank">#sideproject</a> <a href="https://infosec.exchange/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#networking</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a>

Aaron LongchampsNow to the new item functionality.First screenshot shows a summary of test values in the table, and the date is formatted on the frontend so it looks the way I want.Second screenshot shows the new item page which is definitely still a work in progress. I have a lot of functionality to add to this one, and figure out what layout I want to use for it. I'm using things like v-field, v-textarea, and v-date-picker for these elements. The buttons are of course using v-btn.The last screenshot shows the item detail page and this design is definitely not final. I'm not even showing the notes or descriptions fields in this view. I really should sketch out some things I want to do in order to use this the way I want.<a href="https://infosec.exchange/tags/rackroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#rackroot</a> <a href="https://infosec.exchange/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/vuetify" class="mention hashtag" rel="nofollow noopener" target="_blank">#vuetify</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/ux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ux</a> <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://infosec.exchange/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#backend</a> <a href="https://infosec.exchange/tags/sideproject" class="mention hashtag" rel="nofollow noopener" target="_blank">#sideproject</a>

Aaron LongchampsAnd now for some screenshots.First screenshot shows the landing page with basic summaries.Second screenshot shows the new device type tab on the settings page.Third screenshot shows another tab I setup for export/import functionality. That one will be interesting to write, for sure.<a href="https://infosec.exchange/tags/rackroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#rackroot</a> <a href="https://infosec.exchange/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/vuetify" class="mention hashtag" rel="nofollow noopener" target="_blank">#vuetify</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/ux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ux</a> <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://infosec.exchange/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#backend</a> <a href="https://infosec.exchange/tags/sideproject" class="mention hashtag" rel="nofollow noopener" target="_blank">#sideproject</a>

Aaron LongchampsWell, it's been a month or so since I've posted so here's what I've changed/learned about.It was easier for me to use DateTime than Date, even if I just want to hold a Date field. I also started to really build out some of the more dynamic functionality.Device types can now be defined on the setting page, tab 1 and I'm using a modal textbox that pops up when you go to add a new item. All that needs is a name so a model makes a lot of sense for that.When making a new item, the device types are pulled over dynamically and displayed as human-friendly names in a drop down. In the code and going to the back end, it's all using the ID. This field is also nullable in case the device type gets deleted, it won't throw as many exceptions.I also wrote up the item detail page, though both the new item page and item detail page tell me that I need better UX design / more layout experience. This stuff isn't easy!Finally on the design side of things, I've added a couple dynamic boxes to the landing page that show how many items and device types are defined. This is another part of the site I'll work to design more as I go.I'm sure I will find something that looks good and functions the way I want – I just need to get there. And I can tell by where I am now that this project will keep me busy for as long as I want it to.<a href="https://infosec.exchange/tags/rackroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#rackroot</a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/vuetify" class="mention hashtag" rel="nofollow noopener" target="_blank">#vuetify</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/ux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ux</a> <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://infosec.exchange/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#backend</a> <a href="https://infosec.exchange/tags/sideproject" class="mention hashtag" rel="nofollow noopener" target="_blank">#sideproject</a>

Aaron LongchampsThis afternoon's update focused on two things: testing and adding the foreign key relationship to the back end.I re-enabled most of my tests which should make future development a lot faster, updated them a lot to cover the new foreign key for device types on inventory items, and added several tests for device types.I'll integrate this with the front end now that the back end _should_ be good and see how that goes.Latest code is up on my GitHub here <a href="https://github.com/alongchamps/rack-root" rel="nofollow noopener" translate="no" target="_blank">https://github.com/alongchamps/rack-root</a><a href="https://infosec.exchange/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/pytest" class="mention hashtag" rel="nofollow noopener" target="_blank">#pytest</a> <a href="https://infosec.exchange/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> <a href="https://infosec.exchange/tags/vue" class="mention hashtag" rel="nofollow noopener" target="_blank">#vue</a>

Aaron LongchampsI finally have a functional foundation on which to build the front end for Rack Root. For some reason when I was working on it the past few days, the front end code was not cooperating. I reinitialized the project, copied in my existing (previously functional files) and the frontend would just complain about invalid javascript.According to Visual Studio Code, everything looked good. I copied the relevant javascript out and it still looked good, no syntax errors. According to my console, there was a javascript error at the end of the </script> tag in the .vue file.Whatever it was, I re-typed the relevant bits/pieces of my code, checked everything incrementally along the way, and got it back to working again.Now I can start to write more of the back end code, get it all tested, write the front end to go with it, and so on. Repeat until 'done' ;)<a href="https://infosec.exchange/tags/rackroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#rackroot</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://infosec.exchange/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/vue" class="mention hashtag" rel="nofollow noopener" target="_blank">#vue</a> <a href="https://infosec.exchange/tags/vuetify" class="mention hashtag" rel="nofollow noopener" target="_blank">#vuetify</a> <a href="https://infosec.exchange/tags/vite" class="mention hashtag" rel="nofollow noopener" target="_blank">#vite</a>

Aaron LongchampsOver the past few days, I've worked on a design document and started to generate some code for the front end for Rack Root. Now that I have some basis for the tables, I can start putting in the pydantic code to establish the object types, which also means I can start writing the CRUD operations on the back end.Once that's in place, I plan to go after the basic skeleton of the frontend code such as setting up the navigation bar, settings page, and basic inventory operations.<a href="https://github.com/alongchamps/rack-root/blob/main/design.md" rel="nofollow noopener" translate="no" target="_blank">https://github.com/alongchamps/rack-root/blob/main/design.md</a><a href="https://infosec.exchange/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#development</a> <a href="https://infosec.exchange/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/fullstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#fullstack</a> <a href="https://infosec.exchange/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/vue" class="mention hashtag" rel="nofollow noopener" target="_blank">#vue</a> <a href="https://infosec.exchange/tags/rackroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#rackroot</a>

Aaron LongchampsI'm learning a lot more about how Vue works and I am liking it a lot. I now have full CRUD operations on:Get all items Get single item details Edit item (via HTTP PUT)* Create new item and redirect to the new item's detail page Delete item from the 'all items' page Delete item from the single item details page* I also wrote a new backend API for the HTTP PUT operation and associated tests. I already had HTTP PATCH /items/{id}, but that didn't work with my existing code for the front end. I think Vue has a good way to do this with watchers, but I don't have enough understanding of that yet to use it. Maybe that's next!As I've been going through this, I really got a good understanding of how to write APIs, how to name fields, leverage JSON, and other fun things. I like how it's coming together in Vue and plan to keep going with it.I'm not doing anything yet with error handling so I know I need to start incorporating that. I also want to take a look at the watcher mechanisms.<a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://infosec.exchange/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/vue" class="mention hashtag" rel="nofollow noopener" target="_blank">#vue</a> <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://infosec.exchange/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#html</a>

Aaron LongchampsSuccess - this is the line that took me entirely too long to write today:itemsAffected = db.query(Item).filter(Item.id == item_id).update(dict(**foo.model_dump(exclude_unset=True)))with a database session query the Item table for rows that match my item_id update them with properties present in object foo (which is of type ItemUpdate) as a dictionaryThere might be a better way for me to do this, but I didn't find an example online that lined up closely with what I was trying to do.I did not want to have repeating code where it was repeating this for every property or even a foreach loop doing something similar, that feels inefficient:if db_item.<field> != input_item.<field> db_item.<field> = input_item.<field>The Pydantic ItemUpdate has two properties: name and description. The model for the ItemUpdate class defaults to None for everything not specified so you can pass in just { "name": "newnamehere" } and the description property will remain untouched.Now I just need to write tests against this to make sure it's all passing properly!<a href="https://infosec.exchange/tags/fastapi" class="mention hashtag" rel="nofollow noopener" target="_blank">#fastapi</a> <a href="https://infosec.exchange/tags/pydantic" class="mention hashtag" rel="nofollow noopener" target="_blank">#pydantic</a> <a href="https://infosec.exchange/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Recent searches

Search options

Administered by:

Server stats:

#fastapi