Skip to content

Should texture parsers be public API? #7564

New issue
New issue
Open
#7878
Open
Should texture parsers be public API?#7564
#7878
Assignees
slimbuckmvaligursky
Labels
area: assetsarea: graphicsGraphics related issuedocsDocumentation related
@willeastcott

Description

@willeastcott
willeastcott
opened on Apr 14, 2025

Currently, we have the following classes exposed in the API reference:

  • TextureParser
  • BasisParser
  • DdsParser
  • HdrParser
  • ImgParser
  • KtxParser
  • Ktx2Parser

Instances of these classes are created in the TextureHandler constructor and saved to TextureHandler#parsers:

engine/src/framework/handlers/texture.js

Lines 141 to 147 in 62c1c7f

this.parsers = {
dds: new DdsParser(assets),
ktx: new KtxParser(assets),
ktx2: new Ktx2Parser(assets, device),
basis: new BasisParser(assets, device),
hdr: new HdrParser(assets)
};

But this object is not public API. So the question is:

  • Should we expose TextureHandler#parsers as public API?
  • Or should we hide the various parsers from the public API?

Metadata

Metadata

Assignees

Labels

area: assetsarea: graphicsGraphics related issuedocsDocumentation related

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions