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.

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

fix(router-lite): Router injection and ignoring null/undefined values for query parameters #1859

Merged
merged 3 commits into from
Dec 17, 2023

Conversation

Sayan751
Copy link
Member

@Sayan751 Sayan751 commented Dec 16, 2023

Pull Request

πŸ“– Description

🎫 Issues

Closes #1855 and #1857

πŸ‘©β€πŸ’» Reviewer Notes

πŸ“‘ Test Plan

⏭ Next Steps

Copy link

codecov bot commented Dec 16, 2023

Codecov Report

All modified and coverable lines are covered by tests βœ…

Comparison is base (010a4ad) 88.55% compared to head (be45085) 88.55%.
Report is 60 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1859      +/-   ##
==========================================
- Coverage   88.55%   88.55%   -0.01%     
==========================================
  Files         248      248              
  Lines       22290    22292       +2     
  Branches     5180     5181       +1     
==========================================
+ Hits        19739    19740       +1     
- Misses       2551     2552       +1     

β˜” View full report in Codecov by Sentry.
πŸ“’ Have feedback on the report? Share it here.

@bigopon
Copy link
Member

bigopon commented Dec 17, 2023

Are the tests covering the null/undefined issue? I dont see any tests that have a similar template to the reported issue.

Edit: nvm, i just read the last 2 comments so i got the changes. Im not sure we should be that concerned by the loss of data, because we seem to only have 2 choices: have wrong data or no dat, both should be considered loss to me. Absence of data should be the less bad option probably?

@Sayan751
Copy link
Member Author

Absence of data should be the less bad option probably?

I agree. If you don't see any issue with the changes, then maybe we can go forward and merge it.

@Sayan751 Sayan751 merged commit 6a79bc9 into master Dec 17, 2023
27 of 28 checks passed
@Sayan751 Sayan751 deleted the topic/1857-router-injection branch December 17, 2023 18:48
AureliaEffect pushed a commit that referenced this pull request Jan 26, 2024
2.0.0-beta.10 (2024-01-26)

**BREAKING CHANGE:**

* **enums:** string literal types replace const enums (#1870) ([e21e0c9](e21e0c9))

**Features:**

* **route-recognizer:** support for route parameter constraints (#1862) ([8f29cfd](8f29cfd))

**Bug Fixes:**

* **docs:** various doc fix
* **au-slot:** properly handle nested projection registration (#1881) ([00e8dee](00e8dee))
* **kernel:** stack preserving error logging for console (#1884) ([030bfa1](030bfa1))
* **portal:** remove target marker when deactivated (#1883) ([3db4c17](3db4c17))
* **validation:** evaluation of tagged rules from bindings (#1878) ([43d12f6](43d12f6))
* **validation:** property parsing with lambda and istanbul (#1877) ([71f82cf](71f82cf))
* **router:** store root/default page instruction correctly (#1869) ([84e6380](84e6380))
* **runtime-html:** template wrapping  (#1875) ([bfdaa3b](bfdaa3b))
* **i18n:** handle change of key in t.bind (#1868) ([c185764](c185764))
* **router-lite:** Router injection and ignoring null/undefined values for query parameters (#1859) ([6a79bc9](6a79bc9))
* **router-lite:** injection of Router alias ([6a79bc9](6a79bc9))
* **runtime-html:** fix broken tests ([bfdaa3b](bfdaa3b))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AUR3352: Unexpected state at swap of VPA router-lite: null/undefined in optional parameters
2 participants