> We've been working on a browser compatibility data store & API [2][3]. > > To that, we (think we) need to add a linting tool that will use the > compat data store to make a code compatibility report. > > The question for this group is - can we get someone who knows static > analysis involved now to help us make sure the compat data model is > conducive to generating rules for the linter?
I'm happy to consult. Want to set up 20 minutes to chat sometime? I think it'll be a lot more efficient to do a bursty, high-bandwidth session than for me to try to reconstruct your brain contents from etherpads. For CSS and HTML, you'll barely have to do anything deserving of the term "analysis"; I imagine you'll mostly be checking attribute and property names. But there will be some parsing, and that's one of my favorite things. JS will, of course, be hard and should probably wait for 2.0. We're working on that as well, as part of DXR, so we can share some code. For our 20-minute powwow, how about you bring compatibility schema ideas, I'll bring parsing and analysis knowledge, and we'll figure out how to make them meet in the middle? Cheers, Erik _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
