Skip to content

Conversation

@Junius00
Copy link
Contributor

@Junius00 Junius00 commented Nov 3, 2025

Checklist

  • Component contains License
  • Component contains README.md
  • Component contains idf_component.yml file with url field defined
  • Component was added to upload job
  • Component was added to build job
  • Optional: Component contains unit tests
  • CI passing

Change description

Added in v2.0.0:

  • Make NVS usage optional via Kconfig
  • Refactor trigger logic:
    • Allow more than one trigger per schedule
    • More flexible date constraints
  • Add glue layer for NVS, timer, time, memory allocation, logging implementations used by component:
    • This is necessary for RMNG, which has to compile under normal CMake conditions and cannot rely on ESP-IDF
    • Component still behaves like a normal ESP-IDF component with default implementations
  • Add Unity test app

@github-actions github-actions bot changed the title feat(esp_schedule): v2.0.0 feat(esp_schedule): v2.0.0 (IEC-408) Nov 3, 2025
@Junius00 Junius00 force-pushed the feat/esp_schedule/v2.0.0 branch 2 times, most recently from 89a793e to ad0666e Compare November 5, 2025 04:04
@Junius00 Junius00 marked this pull request as draft November 6, 2025 10:05
@Junius00 Junius00 force-pushed the feat/esp_schedule/v2.0.0 branch from 43b7d67 to da57367 Compare November 7, 2025 03:08
@Junius00 Junius00 force-pushed the feat/esp_schedule/v2.0.0 branch from da57367 to d1e9363 Compare November 7, 2025 03:15
@Junius00 Junius00 marked this pull request as ready for review November 7, 2025 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants