From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <yew-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id C29DC1FF15E for <inbox@lore.proxmox.com>; Tue, 14 Jan 2025 12:45:44 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BAC2C14767; Tue, 14 Jan 2025 12:45:27 +0100 (CET) From: Shannon Sterz <s.sterz@proxmox.com> To: yew-devel@lists.proxmox.com Date: Tue, 14 Jan 2025 12:44:36 +0100 Message-Id: <20250114114440.177877-1-s.sterz@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.033 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [yew-devel] [PATCH yew-widget-toolkit 0/4] update macro tests X-BeenThere: yew-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Yew framework devel list at Proxmox <yew-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/yew-devel>, <mailto:yew-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/yew-devel/> List-Post: <mailto:yew-devel@lists.proxmox.com> List-Help: <mailto:yew-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel>, <mailto:yew-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Yew framework devel list at Proxmox <yew-devel@lists.proxmox.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: yew-devel-bounces@lists.proxmox.com Sender: "yew-devel" <yew-devel-bounces@lists.proxmox.com> this adapts the macro tests to the changes in the macros crate so that they work again. note that for the compile tests we eventually want to use `ui_test` [1] to more flexibly handle things like updated compiler versions in the compilation output. however, this is not packaged yet, so just use the `TRYBUILD=overwrite` environment variable to generate the output for the current compiler version. this only effects one test (`invalid_type`) at the moment. [1]: https://crates.io/crates/ui_test Shannon Sterz (4): macros: update compiler version in invalid_type test macros: update no_clone test to adjust to new additional traits macros: update wrong_comp test to adjust to new additional traits macros: update dummy pwt implementations so that the doc tests succeed pwt-macros/src/lib.rs | 49 +++++++++++++++++++- pwt-macros/tests/builder/invalid_type.stderr | 2 +- pwt-macros/tests/widget/no_clone.rs | 13 ++++++ pwt-macros/tests/widget/no_clone.stderr | 8 ++-- pwt-macros/tests/widget/wrong_comp.rs | 21 ++++++++- pwt-macros/tests/widget/wrong_comp.stderr | 4 +- 6 files changed, 87 insertions(+), 10 deletions(-) -- 2.39.5 _______________________________________________ yew-devel mailing list yew-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel