Weekly: FEB \ Week-4 \ 20th-25th \ 2017 \ [ 10:30 - 11:00 ]

[peeyush-tm]

FEB 22

• nginx -> kong
• standerdise/ define DATA REQUEST
  • headers
  • query parameters
• Admin panel -> admin widgets
• django sites framework per microservice ✅
• define the TC TIMELINES -> MONTH/ WEEK/ DAY
• Work from Jaipur -> Work on V2 -> First week of March

FEB Closing

• 8 Days to go 🕗 : Tick Tock Bitch

  • Logbook (basic)
  • Admin Panel (basic)
  • All the apps must have default style (android native, web native, ios native)
  • hard/soft coded data-component-templates

• Review #1 to #34 - Take out time per day

  • V:2 Pending & Ideas #35
  • V:3 Pending & Ideas #36

• Timelines for Battlefield #42

  • One week per month for V:2

• V:2

  • QR Everywhere
    • V2: Mail - send QR and links to the user app => app.veris.in and steps to add to home screen
    • QR String to Vatika
  • Vatika Integration
  • Merge the phone and email profile
  • backup the email and truncate the table. end this nightmare.

The Black Book

[veris-ankitpopli]

Feb 20th, 2017

Work:

• Setup local environment for subdomain & header routing. Cool Tool: xip.io

TODO:

• Fixes in #36

Feb 21st, 2017

Problems

• switch to header based identification of runtime & widgets
  • django urls are relative & doesn't check domains for routing
  • set up different servers :question: :question:
  • or use django sites framework :question: :question:
  • or figure out a way to do the same using Nginx :question: :question:

Feb 22nd, 2017

Work:

• proxy using get_host(), dropped dj sites approach.
• open API to maintain runtime session. :thinking: but :+1:

TODO:

• admin widgets :thinking:

Feb 23rd, 2017

Work:

• Discussion with @peeyush-tm & @veris-neerajdhiman.
  • Complex Widget (Autocomplete View):
    • jQuery style :+1: . Simple & elegant. It will have a dataSrc. No complex chained action like $render.
    • no need to break it down that much :-1:
  • Proxy approach :no_good_man:. Don't forget Process will soon be non HTTP. :disappointed:
  • Information flow is the key :+1:
• :construction: Admin widgets :thinking: :thinking: :thinking:
• :face_with_head_bandage: widgetception :face_with_head_bandage: :gun:
• :+1: widget to create widget :+1: (almost)

TODO

• New Process ----> Widget Schema Generator (custom URLs and params) :sunglasses:

Feb 24th, 2017

Work

• [client] fixes with dot notation names
• [server] swagger schema for widgets API
• :+1: widget to create widget :+1: (still almost)

Problems:

• Manual Processes to create a widget, and runtime & distributing the runtime. :-1:
  • add a OpenAPI (aka Swagger) JSON to Resources Server.
  • create the required process with a defined structure.
  • add the processes to process locker (to be used by widget)
  • associate the process locker id to the widget.
    • add config data
    • add widget template
  • create a widget locker and link all widgets
  • distribute the runtime to the members

TODO

• Process Discovery :thinking: Process should be created for each resource action automagically. :thought_balloon: Either the Resource Server should publish the process or at least notify the process server whenever resource is added/deleted/updated.
• Admin UI to automate everything described above :point_up:

[veris-neerajdhiman]

Feb 20th, 2017

• Starts with react-Native (Android env setup)
• Continue with React Native

Feb 21th, 2017

• A small ToDo app in android :+1:

Feb 22th, 2017

• Integration of Redux with React-Native
• V2 Support

Feb 23-24th, 2017

• Redux inegration with React-Native.
• 3rd party API calling.

[veris-abhinavanand]

FEB 20th,2017

:face_with_thermometer: sick

FEB 21st, 2017

• :+1: Component's data Persistence done
• V2 android terminal release with bug fixes :beetle:

FEB 22nd, 2017

• :+1: Sync widget data with server
• :-1: BUG: component not updated on first load :face_with_head_bandage:

FEB 23rd, 2017

• Data sync with server
• Terminal App update release :boat:

FEB 24th, 2017

• Operations Data type Validation

[veris-amoghbanta]

20th-22nd** Feb

2 releases of iOS terminal with some new requirements and fixes (20th and 22nd) Deep dive into v3 code, client and server. Working on: Overview of how Appium works and writing unit test cases for v3 client.

P.S.: our final test suite would be Jest, Enzyme and Appium and this would cover almost everything. P.S.S.: Jest team is working in God mode( this tweet ).

23rd of Feb

• Shallow and snapshot tests of v3-client components.
• Current problem stuck on: Way to test native and web components at same time in a single project ( this and this and this too )

24th of Feb

• Added mocking setup for native functions in jest.
• Put on hold: testing of web components (i.e. react-native-web) in the same project (the issues referenced on 23rd are related to this)

On the whole:

• We now have our test suite set up for snapshots, unit tests and code coverage (with example references in this repo).
• Snapshot tests for UI components (Button, TextInput, etc.). A good start but just a start.