Id = 23
Nombre Capitulo = Earth (C-500A)
Tipo = Planet
Dimension = Dimension C-500A
Personaje = ['https://rickandmortyapi.com/api/character/37', 'https://rickandmortyapi.com/api/character/91', 'https://rickandmortyapi.com/api/character/176', 'https://rickandmortyapi.com/api/character/183', 'https://rickandmortyapi.com/api/character/195']
Numero Personaje = ['37', '91', '176', '183', '195']
URL Locacion = https://rickandmortyapi.com/api/location/23


Variable
| Static Public Summary | ||
| public |
ADD |
|
| public |
ADD_COMMENT |
|
| public |
ADD_LIKE |
|
| public |
DELETE_LIKE |
|
| public |
FB_LOGIN |
|
| public |
FOLLOW |
|
| public |
FOLLOW |
|
| public |
INIT |
|
| public |
INIT_DONE |
|
| public |
LEFT |
|
| public |
LIKE |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD |
|
| public |
LOAD_COMMENTS |
|
| public |
LOGOUT |
|
| public |
MIDDLE |
|
| public |
PAGINATE |
|
| public |
RECENT |
|
| public |
RESULTS |
|
| public |
RIGHT |
|
| public |
SEARCH |
|
| public |
TRIGGER |
|
| public |
UNFOLLOW |
|
| public |
UNLIKE |
|
| public |
followUser(userId: *, targetId: *, direction: *): * followUser sends Keen tracking event for user follow |
|
| public |
likePhoto(userId: *, postId: *): * likePhoto sends Keen tracking event for photo like |
|
| public |
viewPhoto(userId: *, postId: *, postAuthorId: *): * viewPhoto sends Keen tracking event for photo view |
|
| public |
viewProfile(userId: *, profileUserId: *): * viewProfile sends Keen tracking event for profile view |
Static Public
public ADD_COMMENT: string source
import {ADD_COMMENT} from 'react/modules/actions/Comments.js'
ADD_COMMENT
public DELETE_LIKE: string source
import {DELETE_LIKE} from 'react/modules/actions/Like.js'
DELETE_LIKE
public LOAD_COMMENTS: string source
import {LOAD_COMMENTS} from 'react/modules/actions/Comments.js'
LOAD_COMMENTS
public followUser(userId: *, targetId: *, direction: *): * source
import {followUser} from 'react/modules/utils/analytics.js'
followUser sends Keen tracking event for user follow
public likePhoto(userId: *, postId: *): * source
import {likePhoto} from 'react/modules/utils/analytics.js'
likePhoto sends Keen tracking event for photo like
public viewPhoto(userId: *, postId: *, postAuthorId: *): * source
import {viewPhoto} from 'react/modules/utils/analytics.js'
viewPhoto sends Keen tracking event for photo view
public viewProfile(userId: *, profileUserId: *): * source
import {viewProfile} from 'react/modules/utils/analytics.js'
viewProfile sends Keen tracking event for profile view


Jubilee Austen Project
HTML 5 & CSS Website
Jubilee Austen was a project for my development class. It was the first website I had coded in a really long time. It was so fun getting back into coding and seeing this page come to life.
Rogue Pickings Project
HTML 5 & CSS from Design Comp
Another website from Design Comp using HTML 5.0 & CSS. My second site from scratch with SkillCrush.


StoreProjection
public struct StoreProjection<ViewAction, ViewState> : StoreType
Not necessarily a store implementation means that this entity holds the source-of-truth of an app. The source-of-truth
should be single a centralized store, where all the state is held. But your Views and ViewControllers not necessarily
need to access this main Store directly, they could, instead, access some proxy
store that simply intermediates
all actions (inputs) and state change notifications (outputs), without actually holding the truth. For more information
on that please check StoreProjection
, and compare it to ReduxStoreBase
.
Well, this unlocks several possibilities like having Store Projections
or View Stores
, which act somehow like
presenters (in MVP pattern) or ViewModels (in MVVM pattern), because this layer can be seen as a simple transformation
of states and actions. The view store will transform State into View State by, for example, applying NumberFormatter or
DateFormatter into numbers and dates from your state and generating strings to be shown in UI labels or text fields.
You can picture that as dozens of small functions, transforming each property individually, or you can group all the
properties in a view item, or view state, containing lots of strings to be used by UI controls, and then the whole
process is a single function from (State) -> ViewState
. In the other direction, you probably want to map UI events
like scrolling, button taps, toggle changes and view lifecycle events (did load, will appear, foreground) into app
actions like save a form, load next page, add to favorites or reload a list of items. Grouping them in an enum of
possible events triggered by the user in a certain view, and you may want to map these view actions into app actions:
(ViewAction) -> AppAction
.
Because the StoreType
protocol is very generic and offers ActionHandler
and StateProvider
, we can think of other
possible implementations like a proxy view store that knows how to reach the main store, but exposes to a view only
what’s relevant for it (ViewState
and ViewAction
), at the same time it knows how to map (State) -> ViewState
and
(ViewAction) -> AppAction
. These two transformations are used every time a view dispatches a view action or a state
changes and notifies all subscribers.
Some store implementations will glue all the parts together and become responsible for being its responsibility is
being a proxy to the non-Redux world. For that reason, it’s correct to say that a StoreType
is the single point of
contact with UIKit
and it’s a class that you want to inject as a dependency on all the ViewControllers, either as one
single dependency or, preferably, a dependency for each of its protocols - EventHandler
and StateProvider
-, both
eventually pointing to the same instance.
-
Declaration
Swift
public var statePublisher: UnfailablePublisherType<ViewState>
-
Declaration
Swift
public init(action: @escaping (ViewAction) -> Void, state: UnfailablePublisherType<ViewState>)
-
Declaration
Swift
public func dispatch(_ action: ViewAction)


. I'm a Brazilian web development student at University of
Minnesota,USA. I've started in tech field after moving from Brazil to
Minnesota, with the challenge of changing career.
. My background includes over 20 years of experience as a Safety Work
Engineer and 4 years as a Lawyer and Teacher.
. I'm absolutely curious and dedicated, and as a student, I hope to be
able, very soon, to provide to her clients a special and lucrative
experience with web development services.
A web app where the user can create a playlist based on the travel time. Uses 2 APIs.
For newborn parents, this app will suggests names for babies based on terms like smart, happy, brave etc. It uses Web Scraping in order to get the names.
A fun and interactive game for web browser, developed in Javascript.
Bamazon was constructed using Nodejs to get the user requests by the command line inputs and gives back informations about products, quantities and price from a database, using MySQL Workbench. Bamazon uses too NPM packages.
Train Schedule is a dynamic application created to allows users to incorporate some informations about trains, like name, destination, frequency, etc, and it will see what time will be the next arrival and how many minutes remain until the next ride.
A GIPHY API dynamic web page with gifs of the most popular series on TV.
LIRI was constructed using NPM Packages and APIs for request informations based on the command line user inputs on the and gives back data.