miteb-frontend icon indicating copy to clipboard operation
miteb-frontend copied to clipboard

Post events

Open dheeraj-coding opened this issue 7 years ago • 10 comments

Description

Implement the post events feature to collect data after completion of event.

Type of Change:

  • [x] New feature (non-breaking change which adds functionality)

dheeraj-coding avatar Dec 15 '18 16:12 dheeraj-coding

Run npm run test

bhawesh96 avatar Dec 15 '18 17:12 bhawesh96

Fixed linting issues.

dheeraj-coding avatar Dec 15 '18 17:12 dheeraj-coding

@bhawesh96 @rsarky check the new updates and tell me for further changes.

dheeraj-coding avatar Jan 13 '19 07:01 dheeraj-coding

Can you rebase on master.

rsarky avatar Jan 14 '19 13:01 rsarky

so the feature is fine?

dheeraj-coding avatar Jan 15 '19 05:01 dheeraj-coding

There are some issues.

  1. postEventContainer.js and postEventContainer1.js
  2. this.handleNotes does not exist in postEventContainer.js
  3. Db updates are skewed.
  4. Where are you using postEventFlag?
  5. I can submit the details without entering required fields - number of participants (total and external)

Arushi1912 avatar Jan 15 '19 09:01 Arushi1912

ping @dheeraj-coding

rsarky avatar Jan 21 '19 13:01 rsarky

There are some issues.

  1. postEventContainer.js and postEventContainer1.js
  2. this.handleNotes does not exist in postEventContainer.js
  3. Db updates are skewed.
  4. Where are you using postEventFlag?
  5. I can submit the details without entering required fields - number of participants (total and external)

@dheeraj-coding can you please check these points? I don't see the changes.

Arushi1912 avatar Mar 17 '19 14:03 Arushi1912

@rsarky , do you think we should scrap this and start afresh on this feature? I'm not in sync with this PR at all and I don't think we have support from Dheeraj.

bhawesh96 avatar Apr 07 '20 19:04 bhawesh96

Not sure if any existing work can salvaged from this. We could start afresh if there is someone willing to pick this up! Although I have come to realise some feature additions to the portal tend to get dropped as the contributor loses interest/ has other priorities. Maybe we can set some milestones that can be merged independently for features that are significant sized like this one. That way even if the assignee drops off without completing we have some mergeable work.

rsarky avatar Apr 08 '20 05:04 rsarky