Skip to content
This repository has been archived by the owner on May 28, 2021. It is now read-only.

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

Closed
peeyush-tm opened this issue Feb 20, 2017 · 4 comments
Closed

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

peeyush-tm opened this issue Feb 20, 2017 · 4 comments
Assignees

Comments

@peeyush-tm
Copy link
Collaborator

peeyush-tm commented Feb 20, 2017

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

The Black Book

img_2563
img_2577
img_2578
img_2579
img_2580

@veris-ankitpopli
Copy link
Collaborator

veris-ankitpopli commented Feb 20, 2017

Feb 20th, 2017

Work:

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

TODO:

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 ❓ ❓
    • or use django sites framework ❓ ❓
    • or figure out a way to do the same using Nginx ❓ ❓

Feb 22nd, 2017

Work:

  • proxy using get_host(), dropped dj sites approach.
  • open API to maintain runtime session. 🤔 but 👍

TODO:

  • admin widgets 🤔

Feb 23rd, 2017

Work:

  • Discussion with @peeyush-tm & @veris-neerajdhiman.
    • Complex Widget (Autocomplete View):
      • jQuery style 👍 . Simple & elegant. It will have a dataSrc. No complex chained action like $render.
      • no need to break it down that much 👎
    • Proxy approach 🙅‍♂️. Don't forget Process will soon be non HTTP. 😞
    • Information flow is the key 👍
  • 🚧 Admin widgets 🤔 🤔 🤔
  • 🤕 widgetception 🤕 🔫
  • 👍 widget to create widget 👍 (almost)

TODO

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

Feb 24th, 2017

Work

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

Problems:

  • Manual Processes to create a widget, and runtime & distributing the runtime. 👎
    • 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 🤔 Process should be created for each resource action automagically. 💭 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 ☝️

@veris-neerajdhiman
Copy link
Collaborator

veris-neerajdhiman commented Feb 20, 2017

Feb 20th, 2017

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

Feb 21th, 2017

  • A small ToDo app in android 👍

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
Copy link
Collaborator

veris-abhinavanand commented Feb 22, 2017

FEB 20th,2017

🤒 sick

FEB 21st, 2017

  • 👍 Component's data Persistence done
  • V2 android terminal release with bug fixes 🪲

FEB 22nd, 2017

  • 👍 Sync widget data with server
  • 👎 BUG: component not updated on first load 🤕

FEB 23rd, 2017

  • Data sync with server
  • Terminal App update release ⛵

FEB 24th, 2017

  • Operations Data type Validation

@veris-amoghbanta
Copy link
Collaborator

veris-amoghbanta commented Feb 22, 2017

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants