On 12/5/22 1:26 PM, Chris H-C wrote:
You can drop the query params, for sure. GLAM'll populate them with defaults or the current values (if this isn't the first time the user's visited GLAM). One note is GLAM is presently behind LDAP. Not sure if searchfox has any best practices about linking to non-public resources.
I'm planning to add a new settings page (https://bugzilla.mozilla.org/show_bug.cgi?id=1703656) that will let people opt-in or opt-out of various functionality, especially for cases like the context-menu where users may prefer a minimal experience. I'll be sure to put GLAM behind a setting that will allow someone to indicate they don't have LDAP and don't want to see the LDAP options. (Searchfox has no LDAP awareness at this point and would be dependent on the user indicating whether they have access.) I'd probably make all of this an opt-out since it is useful and extremely specific to these symbols.
As for automation that produces taskcluster artefacts, there is not any of that at present. However, there are plans for the future to get taskcluster to act a little like the github action[1] that's responsible for updating the pipeline to any new metrics or pings. And, if you wanted to build something, glean_parser[2] is not only available in-tree, it's also on pip. You can use that to parse the metrics and pings files in the tree, and then extract whatever meaning you might like. See toolkit/components/glean/build_scripts/glean_parser_ext for the glean parser extensions we've added to Firefox.
Thanks! It looks like the magic definition mechanism comes from a custom constructor in a custom loader at https://github.com/mozilla/glean_parser/blob/4e2b16193703a6195f9d59e420a8a9fa3e7070ef/glean_parser/util.py#L114 so that probably suggests that the tree-sitter approach of https://bugzilla.mozilla.org/show_bug.cgi?id=1800016 would probably be the most pragmatic for my purposes at this time since searchfox's interests are more about syntax highlighting than the higher level semantics glean_parser derives. Also, I see there are schemas at https://github.com/mozilla/glean_parser/tree/4e2b16193703a6195f9d59e420a8a9fa3e7070ef/glean_parser/schemas (woo!) which means that if the searchfox tooling for that is schema-aware (which seems feasible), it could still do some neat stuff.
And, if you'd like a more real-time conversation to happen, you can find me and my teammates over here: https://chat.mozilla.org/#/room/#glean:mozilla.org
Also thanks! I'll definitely be sure to continue the conversation there and/or on bugs (and cc you) as appropriate. Ideally I'll have a proof-of-concept in the new calendar year that can serve as a basis for additional discussion and iteration.
Andrew -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/fe9e661b-08c9-7b10-c684-842b3884f367%40asutherland.org.
