-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
caf: modules: added a custom command to the shell #11927
Conversation
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
ef0de99
to
ff963d0
Compare
Looks good to me. You'll need to update the changelog and this page: |
d61389c
to
32fc050
Compare
32fc050
to
d2d09e8
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, only minor tweaks
Also please check the code owners for CAF to make sure we didn't miss them by accident since this code changed locations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's ok.
We actually wanted to add injecting events but there was never enough time to do it. We can start with this change.
I originally thought injecting could actually be done in type agnostic way. The arguments could be event name (used to extract type id from section) and raw event data (that would have to be formed by the caller based on type). Maybe we should add it...
@MarekPieta , can you have a look? |
d2d09e8
to
3b74583
Compare
3b74583
to
048acd9
Compare
048acd9
to
983efe4
Compare
@peknis I added a new shell module for CAF. How should I change the docs? thanks |
I'd believe you need to write a piece of the new module in \ncs\nrf\doc\nrf\libraries\caf |
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
Thank you so much. I didn't know these exist. There are docs for other issues that I've been having too. |
983efe4
to
dc9a4c8
Compare
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
dc9a4c8
to
b9ed49b
Compare
@MarekPieta Thank you so much for your detailed review. I'll update the docs today. |
b9ed49b
to
f44d437
Compare
f44d437
to
7de06c3
Compare
Added a shell module to the Common Application Framework, and added a custom command to that shell to simulate button press event. Signed-off-by: Tony Le <tony.le@nordicsemi.no>
7de06c3
to
a5cb384
Compare
Added a custom command to simulate a button pressed event to the app_event_manager shell. This command then will be send using RTT in our nrf_cloud_rest_cell_location sample (with RTT Kconfigs enabled).