Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

linkedin - filter posts by type via callback functions #61

Closed
mrWh1te opened this issue Aug 27, 2020 · 0 comments
Closed

linkedin - filter posts by type via callback functions #61

mrWh1te opened this issue Aug 27, 2020 · 0 comments
Labels
botaction enhancement New feature or request proposal New feature or change

Comments

@mrWh1te
Copy link
Owner

mrWh1te commented Aug 27, 2020 •
edited
Loading

Blocked by #38 & #60

Add callback functions for case() to "filter" match post by use-case (post type) for different assembled logic

See #56 (comment)

Then update likeAllFrom() to run varying "liking" assembled logic for the various cases

Finally, update linkedin example to verify results

Related/duplicate:
@mrWh1te mrWh1te added proposal New feature or change botaction enhancement New feature or request labels Aug 27, 2020
This was referenced Aug 27, 2020
Merged
Merged
This was referenced Sep 4, 2020
Merged
Merged
mrWh1te added a commit that referenced this issue Sep 9, 2020
@mrWh1te
pipeCases()() and LinkedIn likeArticlesFrom() (#75)
e968078 
* pipeCases()() and likeAllFrom() #61 #55 
- pipeCases()() like pipeCase()() except ALL cases must match for it to
  return a MatchesSignal with matches and pipeValue
- LinkedIn likeAllFrom(...peopleNames) uses switchPipe() and
  pipeCase()() to test post for type
* Renamed MatchesSignal -> CasesSignal + new prop `conditionPass`
- added `conditionPass` property to CasesSignal so it can return
  matching cases while still presenting itself as not ran since
  the overall condition failed (did not pass)
* pipeCases()() unit-tests
* pipeCases()() & pipeCase()() abortlinesignal tweak
- similar to switchPipe handling abort line signals, it takes multiple
  abort assembledLines to fully abort out of pipeCase(s) cz its 1 to
  abort the line assembled and a second to abort the CasesSignal return
  versus an AbortLineSignal return
- if pipeValue returned, it was abort(2)'s pipeValue
* pipeAbort(), house cleaning, conditionalCallbacks
* pipeCase(s) specifies type CaseValues for callback of testable value
* pipeAbort() supports conditional callback or a pipevalue to test
  against pipevalue and if true, then return AbortLineSignal(1,
  pipeValue?)
* linkedin example using likeArticlesFrom()
- going beyond function scope but to show a more detailed example on how
  a feed could be processed with switchPipe()()
* introduced new botaction scrollTo() which includes a static wait of
  2.5 seconds for the scroll to finish (add more if you need more)
- this update includes the ability to let the LinkedIn app lazily load
  each post if it hasnt been loaded yet, with a special check
- complete but not recently tested likeArticle() functionality since using
  fictional character names
* helpers/navigation unit-testing
* helpers/cases unit-test
* navigation/actions unit-test scrollTo()
* evaluate() botaction with integration test
@mrWh1te mrWh1te closed this as completed Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
botaction enhancement New feature or request proposal New feature or change
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mrWh1te