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

Issue #671: MatChipSet.SelectedChips should match on Label, not MatCh… #672

Open
wants to merge 69 commits into
base: master
Choose a base branch
from

Conversation

petert1401
Copy link

…ip hash.

rokx and others added 30 commits June 17, 2020 16:28
Mentioned that internet access is required in Prerequisites.
…ts-with-docker

Simplify deploying js/css
…? is true or false since it triumphs the checked/ not checked state
…MatBlazor into stefanloerwald-immediate-slider

# Conflicts:
#	src/MatBlazor/wwwroot/dist/matBlazor.js
- Changed DOM and JS for many components, because of changes in MDC Web 7.0.0
- Fixed: Floating label in Outlined MatTextField-based components
- Fixed Validation via EditContext colors
Fixed a null reference exception.
…the hoistToMenu call in matSelect.js, as the full width of the menu must relate to the correct parent.
enkodellc and others added 4 commits September 2, 2020 11:14
…anloerwald](https://github.com/stefanloerwald))

Added - if FullWidth is false - hoistToBody returned
- PR: Cleanup SamProf#673 (Thanks to [stefanloerwald](https://github.com/stefanloerwald))
- PR: Table Re-Rendering Fix SamProf#692 (Thanks to [erlendp](https://github.com/erlendp))
- PR: Custom Drawer Width Demo. Readme contribution updates SamProf#701
@SamProf
Copy link
Owner

SamProf commented Sep 5, 2020

Why MatChip instance is not good?

Spaces in folder name's break DemoContentGenerator.Generate()
PR SamProf#642. Fixes SamProf#619 Validation styles for outlined Text fields
Remove event on Dispose instead of adding one
…lds SamProf#702 (Thanks to [enkodellc](https://github.com/enkodellc))

- PR: Remove event on Dispose instead of adding one SamProf#703 (Thanks to [LeoVen](https://github.com/LeoVen))
@Christian-Oleson
Copy link
Contributor

@petert1401 , looks like there are merge conflicts 😱

@ghost
Copy link

ghost commented Oct 14, 2020

DeepCode's analysis on #059947 found:

  • ℹ️ 1 minor issue. 👇

Top issues

Description Example fixes
No catch method for promise. This may result in an unhandled promise rejection. Occurrences: 🔧 Example fixes

👉 View analysis in DeepCode’s Dashboard | Configure the bot

@petert1401
Copy link
Author

petert1401 commented Oct 14, 2020

@Christian-Oleson Merge conflicts resolved (by pulling latest code from MatBlazor.master)

@Christian-Oleson
Copy link
Contributor

@petert1401 ,
There are also deepcode analysis failures to resolve. 😄

@petert1401
Copy link
Author

@Christian-Oleson, when I originally submitted this, it was a simple 2-line change to MatChipset.cs

Because of delays in reviewing & merging, that cascaded into 135 file merges - one of which is the deepcode issue with MatSlider.cs. It's nothing to do with the original commit to MatChipset and I don't see why I should be expected to resolve it - it should've been resolved when the MatSlider code was last updated.

Maybe the easiest thing to do would be to ditch this pull request and redo the original 2-line change on a fresh branch. Then review & merge it promptly.

@Christian-Oleson
Copy link
Contributor

Christian-Oleson commented Dec 14, 2020

@Christian-Oleson, when I originally submitted this, it was a simple 2-line change to MatChipset.cs

Because of delays in reviewing & merging, that cascaded into 135 file merges - one of which is the deepcode issue with MatSlider.cs. It's nothing to do with the original commit to MatChipset and I don't see why I should be expected to resolve it - it should've been resolved when the MatSlider code was last updated.

Maybe the easiest thing to do would be to ditch this pull request and redo the original 2-line change on a fresh branch. Then review & merge it promptly.

Unfortunately, I don't have anything to do with that portion. The deepcode failures are regarding an uncaught promise, and an unnecessary assignment. If you could fix those two items, at least it would no longer be blocking this PR.

Also, right now this PR is pointed at master. It should be pointed to Dev

@peterthomastlc
Copy link

@Christian-Oleson, no sorry, that uncaught promise is nothing to do with the code I've submitted, neither is the unnecessary assignment - they should be fixed by the original authors. Maybe the cause is that the PR is pointing at master instead of dev?

I suggest you ditch this PR & redo the 2-line fix on a fresh branch.

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.

None yet