yvanzo, monkey: As I was refreshing my memory why companies prefer using Objection.js (https://github.com/Vincit/objection.js/issues/1069 which also convinced me to select it instead of other TypeScript ORMs or query builders in 2021), I've found out some sad news:
Hmm, I already had a look at those (and others), and they're much heavier ORM frameworks whereas Objection is more like an enhanced query builder with support for lazy loading.
iconoclasthero
and since the boot i downloaded said it was an EC boot, i started there. then i looked at the cover and it's actually a BB boot.
so I went to BB and switched the view to Alll release groups
kellnerd: I see. Yes, that would be ideal, especially in view of our ORM issues
kellnerd
Yeah, personally I'm not really a fan of these full blown ORMs and originally intended to go just with Knex (for my personal project) before I discovered Objection back then.
BrainzGit
[listenbrainz-server] 14MonkeyDo merged pull request #2396 (03master…dependabot/npm_and_yarn/braintree/sanitize-url-6.0.1): Bump @braintree/sanitize-url from 6.0.0 to 6.0.1 https://github.com/metabrainz/listenbrainz-serv...
reosarevok
bitmap, yvanzo: so, meeting or no meeting? :D
bitmap
what's on the agenda, entity naming?
yvanzo
yep
bitmap
I suppose I should address the comments in the Flow PR and we can merge that
then continue looking at other CoreEntityT uses?
kellnerd
monkey: But I don't know whether that makes sense for BB. The ideal outcome would be that Objection continues to be maintained, IMO. Maybe there's still hope, according to https://www.npmjs.com/package/objection kibertoad has accepted the NPM invitation at least.
MBS-8186: Extend release group filtering to all sets of RGs, not just official by this artist
iconoclasthero
okie dokie
thanks
yvanzo
added you to followers
iconoclasthero
thanks
bitmap
reosarevok: yvanzo: should we try to resolve the discussion in that PR today? :)
yvanzo
yes
added a list of new types to the PR's description
bitmap: I thought that we would refine types depending on components’ needs (that is specifying need properties, what I tried to do with MergeLink) rather than hard-coding a list of entity types (as in MergeableEntityT/MergeableEntityTypeT).
bitmap
in that case I think it made the types a lot more complicated, because we needed the component to accept a type parameter IIRC
I agree we don't need a list-of-types type in all cases
the list-of-types is mainly useful if you need to refine the type to a more specific one using the entityType property, so that you can access other entity-specific properties.
iconoclasthero
TBH, if there was an option to filter by unofficial release groups, that would make my entries of bootlegs easier
that should be since it's an oakland show around NYE
though prehaps not the etree 84986 version
Since until recently etree wasn't an option for label number
there's also no good place for torrent hashes or names
i usually put them in the disambiguation
bitmap
reosarevok: yvanzo: not sure what to do about the CoreEntityT usage in e.g. EntityHeader. since that uses EntityLink, it will have to be a union type. so, we could use RelatableEntityT, but it's not clear that EntityHeader is only for relatable entities.
reosarevok
Well, we should probably use it for whatever we expect to use it
So if it's only Relatable right now, use that, if not, make a union type?
jasje_ joined the channel
jasje_ has quit
bitmap
sure. RelatableEntityT works fine, so I may be overthinking it
you will still have to ctrl+f, but if it exists it should be on the first page
yvanzo
bitmap: Would it be possible to generate TaggableEntityT type declaration from entities.mjs?
iconoclasthero
is there any way that the entry box for annotations could be expanded rightward?
yvanzo
We have had issues with mismatch between entities.json and Perl code, we don’t want to have it again in JS code.
bitmap
it's technically possible, but no code exists to generate types like that yet
yvanzo
iconoclasthero: It is possible in the annotation editing form that can be accessed from “Edit annotation” link below the annotation display.
bitmap
but, if you tried to use SidebarTags or TagEditor etc. from an entity page that isn't in TaggableEntityT, it will error. so they shouldn't really silently become out of sync
iconoclasthero
yvanzo is that only after the entry's been submitted the first time?
yvanzo
iconoclasthero: yes
iconoclasthero
I don't know what those Tag things are so moot.
yvanzo
It's a different topic as we are having our weekly MB dev meeting atm.
iconoclasthero
ok, later
iconoclasthero has left the channel
yvanzo
It still is code duplication.
It might be possible to add a type to Taggable*T that is not in entities.json.