Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch registration to key first #17679

Open
nik9000 opened this issue Apr 12, 2016 · 2 comments
Open

Switch registration to key first #17679

nik9000 opened this issue Apr 12, 2016 · 2 comments
Labels
:Core/Infra/Core Core issues without another label >enhancement help wanted adoptme Team:Core/Infra Meta label for core/infra team

Comments

@nik9000
Copy link
Member

nik9000 commented Apr 12, 2016

We've been reworking registration of things (query, score function, other stuff) so you register a ParseField, a parser, and reader. Right now the order is reader, parser, parseField. It'd be more like a map if it were parseField, reader, parser. Should we do that?

@javanna
Copy link
Member

javanna commented Apr 12, 2016

++

@jpountz jpountz added help wanted adoptme and removed discuss labels Apr 15, 2016
@colings86 colings86 added the :Core/Infra/Core Core issues without another label label Apr 24, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@rjernst rjernst added the Team:Core/Infra Meta label for core/infra team label May 4, 2020
@rjernst rjernst added the needs:triage Requires assignment of a team area label label Dec 3, 2020
@jaymode jaymode removed the needs:triage Requires assignment of a team area label label Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >enhancement help wanted adoptme Team:Core/Infra Meta label for core/infra team
Projects
None yet
Development

No branches or pull requests

8 participants