Flow Type | Purpose | Key Features | Use Case |
---|---|---|---|
flow {} |
Creates a cold flow that emits values lazily. | Emits values only when collected. Supports suspending functions. |
Creating custom flows to emit data on demand. |
flowOf() |
Creates a flow from a fixed set of values. | Emits provided values sequentially. Cold by nature. |
Emit predefined values (e.g., configuration settings). |
asFlow() |
Converts collections, sequences, arrays, or ranges to flows. | Supports many standard types. Cold by nature. |
Convert lists or arrays into flows for processing. |
`c |
import React, { | |
forwardRef, | |
PropsWithChildren, | |
useImperativeHandle, | |
memo, | |
useMemo, | |
useCallback, | |
} from 'react'; | |
import { | |
Gesture, |
struct ScreenSize { | |
static let width = UIScreen.main.bounds.size.width | |
static let height = UIScreen.main.bounds.size.height | |
static let maxLength = max(ScreenSize.width, ScreenSize.height) //Gets the Height | |
static let minLength = min(ScreenSize.width, ScreenSize.height) //Gets the Width | |
} | |
//Contains the dimensions of the devices | |
fileprivate struct KeybDimensions{ | |
//iPod touch(7), iPhone 5, iPhone 5s, iPhone 5C, iPhone SE |
var mediaJSON = { "categories" : [ { "name" : "Movies", | |
"videos" : [ | |
{ "description" : "Big Buck Bunny tells the story of a giant rabbit with a heart bigger than himself. When one sunny day three rodents rudely harass him, something snaps... and the rabbit ain't no bunny anymore! In the typical cartoon tradition he prepares the nasty rodents a comical revenge.\n\nLicensed under the Creative Commons Attribution license\nhttp://www.bigbuckbunny.org", | |
"sources" : [ "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4" ], | |
"subtitle" : "By Blender Foundation", | |
"thumb" : "images/BigBuckBunny.jpg", | |
"title" : "Big Buck Bunny" | |
}, | |
{ "description" : "The first Blender Open Movie from 2006", | |
"sources" : [ "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/ElephantsDream.mp4" ], |
import { createContext, forwardRef, useCallback, useMemo } from "react"; | |
import { FlatList, FlatListProps, ViewToken } from "react-native"; | |
import Animated, { useSharedValue } from "react-native-reanimated"; | |
const MAX_VIEWABLE_ITEMS = 4; | |
type ViewabilityItemsContextType = string[]; | |
export const ViewabilityItemsContext = createContext< | |
Animated.SharedValue<ViewabilityItemsContextType> |
/* Copyright 2019 The Android Open Source Project | |
* | |
* Licensed under the Apache License, Version 2.0 (the "License"); | |
* you may not use this file except in compliance with the License. | |
* You may obtain a copy of the License at | |
* | |
* https://www.apache.org/licenses/LICENSE-2.0 | |
* | |
* Unless required by applicable law or agreed to in writing, software | |
* distributed under the License is distributed on an "AS IS" BASIS, |
public class MapViewHolder extends RecyclerView.ViewHolder { | |
private MapViewListItemView mMapViewListItemView; | |
public MapViewHolder(MapViewListItemView mapViewListItemView) { | |
super(mapViewListItemView); | |
mMapViewListItemView = mapViewListItemView; | |
} | |
public void mapViewListItemViewOnCreate(Bundle savedInstanceState) { |
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
I recently wanted to rename a model and its postgres table in a Phoenix app. Renaming the table was simple and documented, but the table also had constraints, sequences, and indexes that needed to be updated in order for the Ecto model to be able to rely on default naming conventions. I couldn't find any examples of what this would look like but was eventually able to figure it out. For anyone else in the same situation, hopefully this example helps.
In the example below, I'm renaming the Permission
model to Membership
. This model belongs to a User
and an Account
, so it has foreign key constraints that need to be renamed.
defmodule MyApp.Repo.Migrations.RenamePermissionsToMemberships do
use Ecto.Migration
Enjoy ! 😄
Download iTerm2 here.