scneptune

class ProjectInformationDetails < ActiveRecord::Migration
  def change
    add_column :campaigns, :air_date, :string, null: false, default: DateTime.now
    add_column :campaigns, :approval_type, :text, array: true, null: false, default: []
    add_column :campaigns, :campaign_department, :text, array: true, null:false, default: []
    add_column :campaigns, :campaign_job_uid, :string
    add_column :campaigns, :distribution_spending, :integer, null: false, default: 0
    add_column :campaigns, :invoice_amount, :integer, null: false, default: 0
    add_column :campaigns, :lead_marketer, :string
    add_column :campaigns, :lead_producer, :string

scneptune

// Existing response looks like 
// from algolia after being indexed.  

shows: [{
  id: 232432,
  type: 'show',
  attributes: {
    title: 'Awesomeness Cares',
    atv_id: '322334asdfasdf',
    eidr: 'asdf2r2r2rwfasdfasdf',

scneptune

Keybase proof

I hereby claim:

• I am scneptune on github.
• I am scneptune (https://keybase.io/scneptune) on keybase.
• I have a public key ASBBIoL_3X8R-Vw7IBwMrhBTb94AcGd_2I3Wd6kOW2ucbwo

To claim this, I am signing this object:

scneptune

This will be considered done when:

• In the "Screening Rooms" tab of the admin section of the Catalogue, there exists a dropdown to filter which type(s) of screening rooms are shown.
  • Drop-down options are: All, Full, Basic
  • If All is selected, then each screening room should have a label above the name of the screening room to indicate the type of screening room: Basic or Full
• In the "Screening Rooms" tab of the admin section of the Catalogue, the search feature interacts with this screening room type drop-down menu (so I can search and filter simultaneously).
• For basic screening rooms, admin users can do the following
  • Edit an existing screening room
  • Edit the name of the screening room
• Edit the carousel order of videos in the screening room

scneptune

Goals

Ticket Description This is the FE work to display the current search results using ES instead of Algolia.

• This will be considered done when;
  • A user searches for an item anywhere in the app using global search and consistent results are displayed
  • Results are displayed in a component that matches production currently
• Existing search attributes are returned as results

scneptune

Seniority

• Work Ethic / Attitude / People Skills
• Organization, Convey
  • Communication, Architecture Docs
• Consideration of Business Goals
• Individual Contributions

scneptune

• https://www.sitepoint.com/organize-large-react-application/ Main takeaways: application structure is broken up by feature functionality, not component type, requires in webpack are shallower so folder traversing is easier,
  actions and reducers live in the same file ala https://github.com/erikras/ducks-modular-redux

-DUCKS: namespace action names within the reducer to prevent collisions ala: "delivery/ADD_DELIVERY_ITEM";

• https://jaysoo.ca/2016/02/28/organizing-redux-application/

scneptune

How this state will work

An example state after making the appropriate get API request to /bulk_deliveries

{
     "deliveryLineItemIds": [
          "39773",
          "41046",
          "41201",

scneptune

Bugfix PLT-409

Problem: When a user goes to save a new episode, there is a potential to double submit an episode/show/ancillary if the user double clicks fast enough

Notes :

• Functionally Complex The current update function for writeEpisode (found in gulp/assets/javascripts/stores/actions/updateActions.js) is hopelessly too complex and not very legiable, and handles both contexts for updating and saving new episodes.