metanorma / iso-10303-templates

Annotated EXPRESS rendering templates for ISO 10303
0 stars 0 forks source link

Module documents: missing mapping specification content (Clause 5.1) #22

Closed kwkwan closed 4 months ago

kwkwan commented 4 months ago

The content in mapping.yaml is not included in the output.

ronaldtse commented 4 months ago

I believe @manuelfuenmayor is currently working on this.

manuelfuenmayor commented 4 months ago

The content in mapping.yaml is not included in the output.

Yes, it is: https://github.com/metanorma/iso-10303-templates/blob/main/modules/_module_mappings.liquid#L174-L231

This from main branch.

@kwkwan which document doesn't show the mapping specification content?

ronaldtse commented 4 months ago

@manuelfuenmayor : @kwkwan was referring to ISO 10303-1064 (from https://github.com/metanorma/iso-10303-srl/issues/208). Can you check that? Thanks.

ronaldtse commented 4 months ago

@manuelfuenmayor I'm actually getting these errors when compiling this document:

No label has been processed for ID change_history
No label has been processed for ID arm
No label has been processed for ID mapping
No label has been processed for ID mim_express
No label has been processed for ID AnnexD
No label has been processed for ID annex_listings
ronaldtse commented 4 months ago

Ahh this is because the module schemas are not in schemas_all.yaml yet. I need to figure out how to fix this.

ronaldtse commented 4 months ago

But there are still these:

No label has been processed for ID change_history
No label has been processed for ID AnnexD
No label has been processed for ID annex_listings
ronaldtse commented 4 months ago
Screenshot 2024-05-09 at 3 03 38 AM

@manuelfuenmayor I can see the content is indeed generated now. Thanks!

ronaldtse commented 4 months ago

But there are still these:

No label has been processed for ID change_history
No label has been processed for ID AnnexD
No label has been processed for ID annex_listings

@manuelfuenmayor could you help check what this is about? I'm going to close this issue for now. Maybe a new issue. Thanks!