# export Published articles for export. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kubo 0.42.0 release: on-demand CID announcements, partial CAR import and export, and reprovide changes DevFeed: [Kubo 0.42.0 release: on-demand CID announcements, partial CAR import and export, and reprovide changes]() Original publisher: [Read original article]() Author: Ipfs Published: 2026-06-08T00:00:00Z Content type: release Language: en Sources: [IPFS]() Topics: [releases](), [version](), [export](), [import](), [migration](), [Routing (disambiguation)]() Tags: [block](), [export](), [gateway](), [import](), [kubo](), [migration](), [other](), [release-notes](), [releases](), [retries](), [routing](), [store](), [terminal](), [version]() ### AI overview Kubo 0.42.0 adds on-demand CID announcements, supports streaming CIDs from standard input, and introduces partial CAR export and import. It also changes providing semantics, fixes pin operations blocked by reprovide cycles, and improves migration retries for older repositories. ### Source excerpt Just released: Kubo 0.42.0! ## Waiting for PostgreSQL 19 - json format for COPY TO DevFeed: [Waiting for PostgreSQL 19 - json format for COPY TO]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-29T12:34:22Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [JSON](), [export](), [data](), [Query (disambiguation)](), [interoperability]() Tags: [command](), [copy](), [data](), [developers](), [export](), [json](), [pg19](), [postgresql](), [query](), [stream](), [uncategorized](), [waiting]() ### AI overview The article discusses a PostgreSQL 19 patch adding a JSON format option to COPY TO. It allows table data or query results to be exported as a stream of JSON objects, one object per line, with an option to wrap the output in an array. ### Source excerpt On 20th of March 2026, Andrew Dunstan committed patch: json format for COPY TO This introduces the JSON format option for the COPY TO command, allowing users to export query results or table data directly as a stream of JSON objects (one per line, NDJSON style). The JSON format is currently supported only ... Continue reading "Waiting for PostgreSQL 19 - json format for COPY TO" ## 5 Key Predictions for the Data Industry in 2026 DevFeed: [5 Key Predictions for the Data Industry in 2026]() Original publisher: [Read original article]() Author: SeattleDataGuy Published: 2026-01-31T19:29:24Z Content type: opinion Language: en Sources: [SeattleDataGuy's Newsletter]() Topics: [data](), [Microsoft](), [Artificial Intelligence](), [export](), [Azure]() Tags: [2026](), [ai](), [azure](), [data](), [export](), [microsoft](), [predictions]() ### AI overview A commentary piece offers predictions about the data industry over the next year or two, including a possible Microsoft Fabric rebrand and the continued gap between demand for AI and companies' reliance on traditional data workflows such as ERP exports to Excel, SFTP, and APIs. ### Source excerpt Hype Cycles, Rebrands, and the Messy Reality of Data ## Backup Buddy: A Simple Tool to Backup Your Website Content DevFeed: [Backup Buddy: A Simple Tool to Backup Your Website Content]() Original publisher: [Read original article]() Author: Dean Hume Published: 2025-12-01T12:33:06Z Content type: tutorial Language: en Sources: [Dean Hume]() Topics: [Tool](), [Website](), [Markdown](), [Command-line interface](), [HTML](), [static-site-generator](), [Git](), [Hugo](), [Jekyll]() Tags: [backup](), [command-line](), [export](), [git](), [how-to](), [hugo](), [jekyll](), [offline](), [portable](), [release](), [static-site-generator](), [tool](), [website]() ### AI overview Backup Buddy is a command-line tool that backs up website content by using a sitemap to download pages, convert HTML to Markdown, and save images and videos locally. The article explains its use for offline reading, migration, search, sharing, and Git version control. ### Source excerpt Have you ever wanted to create a backup of your website or blog? Maybe you're migrating to a new platform, or perhaps you just want a portable archive of your content that you can read offline. I've previously experienced issues with this site going down and ## IPTC export changed in Photos for macOS 26 Tahoe DevFeed: [IPTC export changed in Photos for macOS 26 Tahoe]() Original publisher: [Read original article]() Author: Rob Published: 2025-11-11T11:00:00Z Content type: article Language: en Sources: [Rob Allen]() Topics: [macOS](), [data](), [properties]() Tags: [data](), [exiftool](), [export](), [mac](), [macos](), [photography](), [rodeo-flickr-uploader]() ### AI overview Photos for macOS 26 Tahoe changed JPEG IPTC export behavior: Object Name, Caption-Abstract, and Keywords properties are no longer populated as they were in macOS 15 Sequoia. The export still provides the data through Title, Description, and Subject, and Rodeo version 0.5 was updated to resolve the issue. ### Source excerpt I've recently upgraded my MacBook Air to macOS 26 Tahoe and one thing I noticed was that Rodeo's rules were no longer working. With the help of exiftool, I worked out that when exporting to JPEG from Photos for macOS 26 Tahoe, the Object Name, Caption-Abstract and Keywords IPRC properties were no longer being populated. This is a regression from macOS 15 Sequoia. This is the data from exiftool. Output from macOS 15 Sequoia: $... continue reading. ## ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization DevFeed: [ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-16T16:36:22Z Content type: article Language: en Sources: [Effective Android]() Topics: [App](), [Artificial Intelligence](), [Vibe coding](), [Figma](), [Internationalization (i18n)](), [Cloud](), [User Experience]() Tags: [ai](), [android](), [app](), [app-store](), [building](), [cloud](), [code](), [coding](), [editor](), [export](), [figma](), [i18n](), [ios](), [languages](), [phones](), [templates]() ### AI overview The article introduces ScreenshotWhale, a cloud-based service for creating app store screenshots. It offers a Figma-style layer-based editor, templates, support for Android and iOS device formats, and automatic internationalization during export. The product is in its initial stages and is presented as seeking user feedback. ### Source excerpt Some words for the people who joined the newsletter these days. ## Launching ScreenshotWhale.com 🐋 DevFeed: [Launching ScreenshotWhale.com 🐋]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-13T15:03:52Z Content type: release Language: en Sources: [Effective Android]() Topics: [App](), [Android](), [iOS](), [Internationalization (i18n)](), [export](), [Cloud]() Tags: [android](), [app](), [cloud](), [editor](), [export](), [i18n](), [image](), [ios](), [layer](), [screenshots](), [templates]() ### AI overview ScreenshotWhale has launched as a cloud-based tool for creating app screenshots. It includes an online editor, templates, multilingual export, support for iOS and Android form factors, a mirror feature, app store layout settings, and layered editing. ### Source excerpt The wait is over, screenshotwhale is live today 🎉 ## From ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter DevFeed: [From ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-05-20T09:27:30Z Content type: tutorial Language: en Sources: [Anna J McDougall]() Topics: [data](), [implementation](), [Authentication](), [Back end](), [Front end](), [XML](), [pdf]() Tags: [authentication](), [backend](), [data](), [electronic-patient-record](), [engineering-management](), [export](), [frontend](), [germany](), [healthcare](), [healthtech](), [integration](), [pdf](), [pipeline](), [platform](), [product](), [project](), [software-architecture](), [technical](), [terminal]() ### AI overview This technical post describes HelloBetter's implementation journey from Germany's ePA 2.6 to ePA 3.0. It covers HealthID login, ePA data export, PDF and XML document writing, and the frontend and backend integrations used to connect therapeutic data across systems. The implementation was completed pending BfArm approval. ### Source excerpt From ePA 2.6 to 3.0: A Technical Journey in Healthcare Data Integration for Electronic Patient Records...so far Germany has a bad reputation for digitalisation, so the government's push to implement an electronic patient record ("elektronische Patientenakte" or ePA) for its citizens and residents is a step in the right direction. As an official digital health application ("digitale Gesundheitsapplikation" or "DiGA"), we are obligated to shift to the ePA 3.0 implementation. The government rollout has been plagued with technical difficulties and delays, but we're now at a point where we have completed our implementation successfully, pending BfArm approval. In this post, I want to cover the exact steps we and had to take to achieve this. I want to thank Senior Product Manager Tanja Lembcke and Senior Backend Engineer Chaythanya Sivakumar for their contributions to this piece. The Challenge: Connecting Patient Data Across Systems The electronic patient record (ePA) and HealthID integration project had a clear mission: we wanted to give our patients the ability to log into the HelloBetter platform using their HealthID (which they access through their insurance company) and export their HelloBetter data into their ePA. A successful implementation would mean that both doctors and patients can electronically access therapeutic data whenever they need it. To make this happen for the patient data at HelloBetter, we partnered with two key players: RISE for ePA system access and Azuma for HealthID system access. Our journey began in 2024 when our backend team laid the groundwork for ePA 2.6, setting up the pipeline and data export in our staging environment. We successfully implemented both PDF and XML document writing capabilities, along with the frontend and backend integrations for HealthID login. How It All Works: The Architectural SideHealthID Authentication The first piece of the puzzle is connecting to and authorising the user's HealthID. This part of the system has remai ## USA Could Win By Rolling Back AI Export Controls DevFeed: [USA Could Win By Rolling Back AI Export Controls]() Original publisher: [Read original article]() Published: 2025-01-28T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [AI Development](), [deepseek](), [CUDA](), [Compiler](), [Nvidia](), [Machine learning](), [networking](), [huawei]() Tags: [ai](), [compiler](), [cuda](), [deepseek](), [export](), [machine-learning](), [networking](), [nvidia]() ### AI overview This opinion argues that the United States could preserve its AI lead by rolling back export controls on advanced AI chips. It describes how DeepSeek reportedly trained R1 on H800 GPUs and allegedly worked around bandwidth restrictions by writing low-level code directly, while using Huawei 910C NPUs for serving. ### Source excerpt This might sound crazy to just about everyone, but I think Trump could maintain an AI lead for the United States by immediately rolling back Biden-era export controls on AI chips, like the NVIDIA H100. Hear me out! ## The Making of a Logo DevFeed: [The Making of a Logo]() Original publisher: [Read original article]() Author: Paul Lewis Published: 2025-01-15T00:00:00Z Content type: opinion Language: en Sources: [Paul Lewis]() Topics: [Website](), [blender](), [3D](), [stl](), [SVG](), [export](), [render](), [Sketch]() Tags: [3d](), [3d-printed](), [blender](), [cameras](), [export](), [file](), [logo](), [making](), [render](), [stl](), [svg](), [update](), [website]() ### AI overview The author describes creating a new Aerotwist logo, starting with sketches on a reMarkable 2 tablet, refining it as a vector and SVG, and preparing it for 3D printing by exporting an STL from Blender. ### Source excerpt A new website, and a 3D printed logo! ## Insights from Workflow History Export on Temporal Cloud DevFeed: [Insights from Workflow History Export on Temporal Cloud]() Original publisher: [Read original article]() Author: Alice Yin Published: 2024-04-24T06:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [export](), [Amazon S3](), [Data pipelines](), [Data analysis](), [parquet](), [airflow](), [AWS Glue]() Tags: [airflow](), [amazon-s3](), [api](), [aws-glue](), [case-study](), [data](), [data-analysis](), [data-pipelines](), [export](), [parquet](), [product-news]() ### AI overview This tutorial explains how to export closed workflow histories from Temporal Cloud to Amazon S3, convert Protocol Buffer files to Parquet, and build data pipelines for analyzing execution metadata, operational efficiency, and bottlenecks. ### Source excerpt Explore how exporting workflow histories in Temporal Cloud gives you deep insights into execution metadata, events, and performance over time. ## Introducing Workflow History Export DevFeed: [Introducing Workflow History Export]() Original publisher: [Read original article]() Author: Nikitha Suryadevara Published: 2024-03-01T07:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Amazon S3](), [AWS CloudFormation](), [Amazon Web Services](), [Cloud](), [audit](), [Command-line interface]() Tags: [audit](), [aws](), [aws-cloudformation](), [aws-s3](), [cli](), [cloud-storage](), [export](), [preview](), [product-news](), [production](), [release](), [s3](), [workflow]() ### AI overview Temporal Cloud has introduced Workflow History Export, allowing users to export closed workflow histories by namespace to an AWS S3 bucket. The feature supports longer-term retention for compliance, auditing, and analysis and is available to all users in Public Preview for production use. ### Source excerpt Workflow History Export in Temporal Cloud allows users to export closed workflow histories on a per-namespace basis to an AWS S3 cloud storage bucket. ## Why You Should Execute jOOQ Queries With jOOQ DevFeed: [Why You Should Execute jOOQ Queries With jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-01-18T11:46:25Z Content type: opinion Language: en Sources: [jOOQ]() Topics: [SQL](), [Java](), [Databases](), [Compiler]() Tags: [code-generation](), [crud](), [csv](), [execution](), [export](), [identity](), [import](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [jpa](), [json](), [mapping](), [multiset](), [nested-collections](), [nested-records](), [orm](), [r2dbc](), [sql](), [stored-procedures](), [type-safety](), [udt](), [updatablerecord](), [user-defined-types](), [xml]() ### AI overview The article argues that queries built with jOOQ should generally also be executed with jOOQ. It explains that jOOQ preserves type safety and structured result mapping during execution, whereas extracting SQL and bind values for JDBC-level execution loses compiler knowledge of the result set. It acknowledges limited use cases for executing jOOQ-generated SQL elsewhere, such as a small number of dynamic queries in an otherwise JPA-based application. ### Source excerpt Previously on this blog, I've written a post explaining why you should use jOOQ's code generator, despite the possibility of using jOOQ without it. In a similar fashion, as I've answered numerous jOOQ questions on Stack Overflow, where someone used jOOQ to build a query, but then executed it elsewhere, including on: jOOQ itself isn't ... Continue reading Why You Should Execute jOOQ Queries With jOOQ -> ## Under the hood of Relay, Android Studio plugin for exporting Figma components to compose - Kevin Schildhorn DevFeed: [Under the hood of Relay, Android Studio plugin for exporting Figma components to compose - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2022-11-15T19:45:27Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Figma](), [Compose](), [Android Studio](), [ui]() Tags: [android](), [android-studio](), [code](), [components](), [compose](), [design](), [export](), [figma](), [plugin]() ### AI overview This article examines how Relay converts Figma components into Compose UI code through its Android Studio plugin. It follows a simple button from Figma export to an imported UI package and discusses the generated files, styles, properties, and fonts. The article notes that Relay is an open-alpha, evolving library and that the observations use version 0.3.00. ### Source excerpt What's going on under the hood with Relay? Let's go over the process in detail, from Figma to Compose code. ## Securely Managing Your Audit Logs with Teleport and Snowflake DevFeed: [Securely Managing Your Audit Logs with Teleport and Snowflake]() Original publisher: [Read original article]() Author: kenneth.dumez@goteleport.com (Kenneth DuMez) Published: 2022-10-11T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [audit](), [Logging](), [Security](), [SIEM, Security, Observability](), [event driven](), [Amazon S3](), [data]() Tags: [audit](), [aws](), [cloud](), [cybersecurity](), [data](), [data-lake](), [data-storage](), [database](), [deployment](), [event](), [event-driven](), [export](), [filter](), [format](), [how-to](), [infrastructure](), [latency](), [logging](), [logs](), [snowflake]() ### AI overview A tutorial explains how to forward Teleport audit logs to Snowflake using Fluentd as a collector, Amazon S3 as an intermediary, and Snowpipe for ingestion. It covers the security, organization, searchability, and low-latency benefits of this workflow for SIEM-related log management. ### Source excerpt How to securely manage all of your event-driven audit logs with Snowflake and Teleport. ## Wearing Many Hats DevFeed: [Wearing Many Hats]() Original publisher: [Read original article]() Author: Adam Published: 2022-01-24T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [networking](), [Software]() Tags: [cryptographic](), [export](), [government](), [history](), [networking](), [report](), [security](), [software](), [surveillance](), [transformation]() ### AI overview The article reviews Wearing Many Hats: The Rise of the Professional Security Hacker, a history of how 1990s hackers established legitimacy as employable and trustworthy security experts. It praises the report while noting that early cypherpunks also addressed surveillance, activist targeting, and cryptographic export controls, with overlap between hacker and cypherpunk communities. ### Source excerpt Fascinating history of a transformation in how hackers were seen. ## Introducing Material Theme Builder DevFeed: [Introducing Material Theme Builder]() Original publisher: [Read original article]() Published: 2021-10-27T09:15:00Z Content type: release Language: en Sources: [Material.io - Material Design]() Topics: [color](), [Code](), [export]() Tags: [code](), [color](), [export]() ### AI overview Material introduces Material Theme Builder, a tool for visualizing dynamic color, building custom themes, and exporting them to code. ### Source excerpt Visualize dynamic color, build a custom theme, and export to code ## Blender SVG Export Experiment DevFeed: [Blender SVG Export Experiment]() Original publisher: [Read original article]() Author: Stanko Published: 2020-10-12T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [blender](), [export](), [SVG]() Tags: [art](), [blender](), [export](), [svg]() ### AI overview An art experiment using Blender's SVG export, resulting in two plots with slightly different sizes because one was cut incorrectly. ### Source excerpt One plot ended up being smaller because I screwed up cutting it. Created: October 2020Size: 15x15cm and 13x13cmPaper: Fabriano Bristol 250gsmPens: Molotow Blackliner, Koi Coloring Brush, Mechanical pencil ## Three.js extrude SVG path DevFeed: [Three.js extrude SVG path]() Original publisher: [Read original article]() Author: Stanko Published: 2019-12-18T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Three.js](), [SVG](), [3D](), [Graphics]() Tags: [3d](), [demo](), [export](), [getting-started](), [gotchas](), [graphics](), [how-to](), [svg](), [three-js]() ### AI overview A tutorial on importing SVG data into Three.js with SVGLoader and extruding SVG paths into 3D geometry with ExtrudeGeometry. It explains setup details and common issues, including the inverted Y axis when mapping SVG coordinates into Three.js. ### Source excerpt Update, September 2025 # Replaced path.toShapes(true) with SVGLoader.createShapes(path) because toShapes misses some of the SVG-specific logic implemented in the loader. Thanks to forresto who pointed it out. Also updated the demo to use a fresh version of ThreeJS. These days I'm playing with three.js again. I'm not an expert but I enjoy playing with graphics. Conveniently, a friend of mine sent me this Dribble, and I thought it would be a perfect exercise to try making it. I still haven't done it, but I did some exploration on how to built it. My plan was to draw the parallaxing layers as vectors, import it in three.js and use ExtrudeGeometry to give them a third dimension. To three.js ninjas this might be funny, but it took me some time. I haven't found well documented way, plus there are a couple of gotchas. And that is the reason I want to share this process with you. Before we start # I'll assume you have a basic understanding of three.js, and how to setup a scene. If you are just starting with it, I recommend going through their excellent Getting Started guide first. If you just want to see the end result, feel free to jump to the code or the live demo. SVGLoader # Three.js provides us with SVGLoader, but it is not the part of the main export. It is an addon, and can import it like this: import { SVGLoader } from "three/addons/loaders/SVGLoader.js"; Like it's name suggest this class loads SVG from an URL and parses it into three.js entries. If you already have SVG markup as a string, it is easy to parse it, but it is also easy to miss how to do it in the documentation. SVGLoader extends base Loader class, which contains .parse() method. That means we can do this: // Get SVG's markup const svgMarkup = document.querySelector('svg').outerHTML; const loader = new SVGLoader(); const svgData = loader.parse(svgMarkup); Now when we know how to get SVG data to three.js, let's try to extrude it. Extrude # You'll need a SVG, I used my logo: To get to the shapes we can ex ## Remove MacOS Catalina zsh nagging DevFeed: [Remove MacOS Catalina zsh nagging]() Original publisher: [Read original article]() Author: Stanko Published: 2019-12-10T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [macOS](), [Zsh](), [Bash](), [Shell](), [Terminal]() Tags: [apple](), [bash](), [catalina](), [export](), [macos](), [make](), [oh-my-zsh](), [shell](), [terminal](), [zsh]() ### AI overview A guide for silencing the macOS Catalina warning about the default shell changing from Bash to zsh by setting BASH_SILENCE_DEPRECATION_WARNING=1 in .bash_profile or .bashrc. ### Source excerpt Yesterday I updated my work laptop to MacOS Catalina.To be able to use AirPods Pro with it :/ Apple made a change and switched the default shell to zsh (instead of bash). From what I have read, the reason is a licensing issue. Bash is not gone and everything will work like it used to. But every time you open a terminal, you will be greeted by this message: If you are like me, and not ready to make the switch to zsh, you can silence this warning by putting this into your .bash_profile (or .bashrc). export BASH_SILENCE_DEPRECATION_WARNING=1 Why I don't want to switch? # Everything in my workflow is heavily customized and I'm really used to it. For example, I'm using bash-it with a custom theme for years now. It is heavily inspired by Oh My Zsh, similar zsh framework. Still, it will take me some time to migrate everything. I will eventually switch to zsh, but at the moment it is not high on my list of priorities. ## Toolbox: After a Conference DevFeed: [Toolbox: After a Conference]() Original publisher: [Read original article]() Author: Adam Published: 2018-08-21T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Tool](), [To-Do](), [email](), [Slack](), [export]() Tags: [advice](), [email](), [export](), [great](), [organization](), [process](), [slack](), [toolbox]() ### AI overview A personal account of a post-conference follow-up workflow using email, messaging apps, LinkedIn, Workflowy, business cards, Slack, calendars, photos, and social media. The author describes organizing these queues and asks readers to share more effective methods. ### Source excerpt [no description provided] ## Exporting a Hierarchy in JSON: with recursive queries DevFeed: [Exporting a Hierarchy in JSON: with recursive queries]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2018-01-31T17:00:01Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [SQL](), [PostgreSQL](), [export](), [JSON](), [data](), [JavaScript]() Tags: [data](), [export](), [file](), [json](), [postgresql](), [sql]() ### AI overview This tutorial explains how to use PostgreSQL and recursive SQL queries to export hierarchical relational data as a single JSON document. It models parent-child Dungeons & Dragons character classes and prepares the resulting JSON for client-side visualization with d3js. ### Source excerpt In another article here, entitled on JSON and SQL, we saw in great details how to import a data set only available as a giant JSON file. Then we normalized the data set, so as to be able to write SQL and process our data. This approach is sometimes very useful and was a good way to learn some of the JSON functions provided by PostgreSQL. In this article, we're going to use SQL to export the data from our relational model into a JSON document. The trick that makes it complex in this example is that we have a recursive data model, with a notion of a parent row that exists in the same table as the current one. That's a nice excuse to learn more about the SQL construct WITH RECURSIVE. ## React Router v4 redirect decorator DevFeed: [React Router v4 redirect decorator]() Original publisher: [Read original article]() Author: Stanko Published: 2018-01-29T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [React Router](), [React Component](), [Code]() Tags: [code](), [component](), [export](), [import](), [react](), [react-component](), [react-router](), [return](), [router](), [routing]() ### AI overview This tutorial explains how React Router v4 handles redirects through rendered components and presents a higher-order decorator that exposes a redirectTo method. The decorator can either replace the current URL or push a new history entry. ### Source excerpt React Router switched to component based routing starting with the version 4. Redirects are now done by rendering a Redirect component, like this:Please note that you can use included withRouter decorator but it can cause update blocking and introduce side effects. This is small subset of it. What I usually do is to keep redirectTo property in component's state. To redirect, I set it to the URL I want to redirect to, and render Redirect at the start of the render method: render() { const { redirectTo } = this.state; if (redirectTo) { return ; } return ( ); } This approach works well, but I got tired of repeating the same code over and over again. So I pulled the functionality to a decorator (higher order component if you prefer). Redirect decorator # I did exactly what I described above, and exposed redirectTo method to a composed component. import React, { Component } from 'react'; import { Redirect } from 'react-router-dom'; const withRedirect = ComposedComponent => class RedirectDecorator extends Component { state = { push: false, redirectUrl: null, } componentDidUpdate(prevProps, prevState) { const { redirectUrl, } = this.state; // If component is rendered on redirect page as well // (i.e. header or footer) it would cause redirect-loop // as "" is being rendered every time. // So we are resetting the state after redirect if (!prevState.redirectUrl && redirectUrl) { this.setState({ push: false, redirectUrl: null, }); } } redirectTo = (redirectUrl, push = false) => { this.setState({ push, redirectUrl, }); } render() { const { push, redirectUrl, } = this.state; if (redirectUrl) { return ; } return ( ); } }; export default withRedirect; Usage # Import newly added decorator and apply it to your component. It will inject redirectTo to it's props, and ## localStorage and sessionStorage in Safari's private mode DevFeed: [localStorage and sessionStorage in Safari's private mode]() Original publisher: [Read original article]() Author: Stanko Published: 2017-08-09T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [LocalStorage](), [Code](), [App]() Tags: [code](), [error](), [export](), [ls](), [null](), [object](), [qa](), [quota](), [return](), [safari](), [storage](), [test](), [value](), [version]() ### AI overview This article explains that Safari private mode sets localStorage and sessionStorage limits to zero, preventing writes. It presents a localStorage facade that silently ignores storage operations when storage is unavailable, avoiding application errors. ### Source excerpt If you didn't know, in Safari's private mode both localStorage and sessionStorage are not working. To be exact, Safari sets storage's limit to 0, so you can't write anything to it. I keep forgetting this, until QA people report it at some point. So I quickly wrote a small facade for it, which fails silently in this case. That means it still doesn't work but it won't throw an error and break your application. This is the version for localStorage, just replace it with sessionStorage if you need it. const LS_TEST_KEY = 'ls-test'; let isLocalStorageSupported = typeof localStorage === 'object'; // Try to try { localStorage.setItem(LS_TEST_KEY, 'test'); localStorage.removeItem(LS_TEST_KEY); } catch (e) { isLocalStorageSupported = false; // If we get error that we exceeded storage's quota // but storage is still empty we are in private mode if (e.code === DOMException.QUOTA_EXCEEDED_ERR && localStorage.length === 0) { // Private mode } else { throw e; } } const LocalStorage = { getItem: (key) => { if (isLocalStorageSupported) { return localStorage.getItem(key); } return null; }, setItem: (key, value) => { if (isLocalStorageSupported) { localStorage.setItem(key, value); } }, removeItem: (key) => { if (isLocalStorageSupported) { localStorage.removeItem(key); } }, }; export default LocalStorage; [Next page]()