a packaging=gwt-lib is a jar
(its like how a source jar is actually a
.jar, not a .sources)
how did maven central let you release something that depends on a snapshot?
I had a small internal hackathon for micro frontends with JS... And we use GWT... I'll summarize our experiences later...
At any rate, thanks Colin, I will see if I can confirm that. I thought I had cleaned it up and removed any trace of 2.8
any elemento users who have a bit of time to try, we have a candidate 1.0.0-RC1 release for gwt-safehtml in this staging repo: https://oss.sonatype.org/content/repositories/orggwtproject-1043
if all looks good we'll push it to central
@/all I've just released Elemento 1.0.2. It upgrades gwt-safehtml to 1.0.0-RC1
See https://github.com/hal/elemento/releases/tag/1.0.2
See https://github.com/hal/elemento/releases/tag/1.0.2
@/all I've just released Elemento 1.0.3. The only change is that the minimal Java version is now Java 1.8. See https://github.com/hal/elemento/releases/tag/1.0.3
This should help projects which still require Java 8, but want to upgrade to the latest Elemento version
The new version should land in maven central soon.
This should help projects which still require Java 8, but want to upgrade to the latest Elemento version
The new version should land in maven central soon.
@/all FYI I've updated all demos of Elemento (thanks @treblereel for updating the crysknife demo). All demos compile again and are online available at https://hal.github.io/elemento/index.html
?
I cant find valid import
Hi! A question about elemento templates: I have a @DataElement class field called say "user_id". And in the corresponding HTML template file I have an element with attribute 'data-element="user_ID"' so I mistakenly used the wrong case for id/ID. It appears that the elemento annotation processor at compile time doesn't flag this mismatch at compile time. But at runtime the element is not found and not bound to the java object field!? Is this known behaviour? I must confess that I am using a hacked version of elemento-template-* 0.9.6 that depends on elemento-core 1.0.2. I wonder if I have broken something in my hack.
so, what is your build tool, and are you sure it is running the processor when you make any chance at all to the html template?
But I am finding that the compiler finds a case-insensitive match and compiles the template. But at runtime it comes unstuck.
Of course I should be careful to get the cases matching in the first place, but sometimes mistakes are made and I am confused by it compiling OK but not running.
From
TemplatedProcessor: private void verifySelector(String selector, Element element, TemplateSelector templateSelector,
org.jsoup.nodes.Element root) {
// make sure to use the same logic for finding matching elements as in TemplateUtils!
Elements elements = root.getElementsByAttributeValue("data-element", selector);
Which calls the jsoup library:
/**
* Find elements that have an attribute with the specific value. Case insensitive.
...
*/
public Elements getElementsByAttributeValue(String key, String value) {
OK, the way to use JSoup to do a case-insensitive match on attribute name and a case-sensitive match on attibute value is:
//Elements elements = root.getElementsByAttributeValue("data-element", selector);
Elements elements = root.getElementsByAttribute("data-element");
long matchCount = elements.stream().filter(elem -> elem.attributes().getIgnoreCase("data-element").equals(selector)).count();
I'll add an issue to the crysknife-io project, which is where the maintained templating code now lives, @treblereel