In previous threads on the same topic documentation was cited as something holding us back from calling it a 1.0.
There’s also the marketing issue. From what I see, the active members of this community are not keen to take on marketing challenges, and this may not change in the foreseeable future, but ideally we would want to create some sort of buzz, and be ready to face questions following that. Silently bumping to 1.0 may be the best we can do at this point though… The reason I brought up 1.0 on this thread was to decide what version the mvn snapshots will show after 0.9.9. Should we just vote on that? Also, it would be good to pass on some of the knowledge I have gained in previous releases to others here, so this is an opportunity for volunteers to step up. From: Harbs<mailto:harbs.li...@gmail.com> Sent: Tuesday, December 7, 2021 10:15 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: Re: 0.9.9 It’s a bit of a stretch that it’s a concern because even where it’s used, the source is not typically going to be an outside source. I wouldn’t consider it an obstacle for “1.0”, but we should address it. > On Dec 7, 2021, at 10:11 PM, Greg Dove <greg.d...@gmail.com> wrote: > >> That said, we’re using innerHTML in some places in the Framework where it > is not necessary. That should be fixed. > > Yeah, that's actually what I was meaning. I don't know if there are any > other things like this which we might have overlooked, or whether it is > critical to consider these for '1.0' > > > > > On Wed, Dec 8, 2021 at 9:00 AM Harbs <harbs.li...@gmail.com> wrote: > >> In React, there’s a desire to set innerHTML because things are hard to do >> there. In Royale, not so much. >> >> That said, we’re using innerHTML in some places in the Framework where it >> is not necessary. That should be fixed. >> >>> On Dec 7, 2021, at 9:36 PM, Greg Dove <greg.d...@gmail.com> wrote: >>> >>> We discussed at one point the potential security risks associated with >>> using innerHTML in some code, for example and that other frameworks avoid >>> that (React requires that a dev use a method called >> dangerouslySetInnerHTML >>> or something like that). >> >>
