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

chore: add hilla-dev-mode in vaadin-dev #4968

Merged
merged 14 commits into from
Feb 7, 2024

Conversation

tltv
Copy link
Member

@tltv tltv commented Jan 30, 2024

Fixes: #4946

Note! Need to merge first Hilla's vaadin/hilla#2001.

@ZheSun88 ZheSun88 enabled auto-merge (squash) January 30, 2024 14:46
@ZheSun88 ZheSun88 disabled auto-merge January 30, 2024 14:47
vaadin-dev/pom.xml Show resolved Hide resolved
@manolo manolo enabled auto-merge (rebase) January 31, 2024 15:38
ZheSun88 added a commit that referenced this pull request Feb 1, 2024
* repackage vaadin-maven plugin

* reuse flow.version in gradle-plugin

* remove the change for the hilla-dev-mode, as it will be covered by #4968

---------

Co-authored-by: Manolo Carrasco <[email protected]>
@manolo manolo force-pushed the chore/add-hilla-dev-mode-to-vaadin-dev branch 2 times, most recently from 26cff90 to e30cd53 Compare February 3, 2024 08:47
tltv and others added 4 commits February 5, 2024 07:44
But not from the vaadin-core which brings in vaadin-dev with hilla-dev-mode. Excluding vaadin-dev for production builds work better this way.
@manolo manolo force-pushed the chore/add-hilla-dev-mode-to-vaadin-dev branch from 1e41c4f to 192bb55 Compare February 5, 2024 06:44
public void load() {
if (getDriver().getPageSource().contains("<div class=\"message\">Building front-end development bundle</div>")) {
// Wait for the development bundle to be loaded
$(NotificationElement.class).waitForFirst(180);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel that ff the problem is that we need for the bundle to be compiled, probably this fix should be in the testbench instead

@ZheSun88 ZheSun88 force-pushed the chore/add-hilla-dev-mode-to-vaadin-dev branch from 8f00e53 to e142b5d Compare February 6, 2024 11:12
Copy link

github-actions bot commented Feb 6, 2024

Dependencies Report

  • 🟠 Known Vulnerabilities:

    • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/[email protected] [CVE-2023-35116] (owasp)
      👌 Not a valid CVE report based on the vendor analysis and research
      · cpe:2.3:a:fasterxml:jackson-databind::::::::
      • Vulnerabilities in: pkg:maven/me.friwi/jcef-api@jcef-af53d63%2Bcef-104.4.23%2Bg46ae630%2Bchromium-104.0.5112.102 [CVE-2024-21639, CVE-2024-21640] (owasp)
        👌 Wait for the update from the jcefmaven community. Meanwhile the swing-kit is supposed to be used with fixed websites and not to browse the internet, we have a check for that, so the only possible attacker would be the same person that created the swing application, aka our customer devs. so this vulnerability is not classified by us as critical issue
        · cpe:2.3:a:chromiumembedded:chromium_embedded_framework::::::::
  • 📔 No License Issues

[Click for more Details]

@manolo manolo merged commit b193679 into main Feb 7, 2024
3 checks passed
@manolo manolo deleted the chore/add-hilla-dev-mode-to-vaadin-dev branch February 7, 2024 06:19
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.

Include hilla-dev-mode to platform
5 participants